[MAGNOLIA-3079] ComponentProvider should lookup superclasses and interfaces of the required component Created: 13/Feb/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
If ComponentProvider.getSingleton(com.foo.SomeSubInterface.class) is called, and no component is registered specifically for com.foo.SomeSubInterface, the ComponentProvider should look up registration for parents of com.foo.SomeSubInterface (i.e com.foo.SomeInterface, if SomeSubInterface extends SomeInterface) This should:
|
| Comments |
| Comment by Jan Haderka [ 25/Feb/10 ] |
|
And yet another incarnation of the same problem: java.lang.ClassCastException: info.magnolia.module.extendedtemplatingkit.i18n.ETKI18nContentSupport cannot be cast to info.magnolia.cms.i18n.AbstractI18nContentSupport info.magnolia.cms.i18n.DefaultI18nContentSupport$$EnhancerByCGLIB$$a2946d4f.determineLocale(<generated>) info.magnolia.cms.i18n.I18nContentSupportFilter.doFilter(I18nContentSupportFilter.java:60) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:82) |
| Comment by Magnolia International [ 26/Jan/11 ] |
|
Probably becomes irrelevant with |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |