[MAGNOLIA-3054] ContentWrapper requires AbstractContent to work properly Created: 02/Feb/10 Updated: 23/Jan/13 Resolved: 18/Mar/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.3 |
| Fix Version/s: | 4.3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
AbstractContent defines abstract public NodeData getNodeData(String name, int type) throws AccessDeniedException, RepositoryException; method that all extending classes need to implement and ContentWrapper implements this method as well, undiscriminatelly casting Content returned by public Content getWrappedContent();
method into AbstractContent. |
| Comments |
| Comment by Magnolia International [ 02/Feb/10 ] |
|
We should come to a conclusion about this for 4.3 |
| Comment by Philipp Bärfuss [ 04/Feb/10 ] |
|
After overworking the InheritanceContentWrapper I have to back Jan and think we should:
|
| Comment by Philipp Bärfuss [ 04/Feb/10 ] |
|
I have
In my opinion this issue can be closed. Opinions? one, two, three, .. |