[MAGNOLIA-4296] jcr: wrappers Created: 13/Apr/11 Updated: 22/Mar/12 Resolved: 08/Jun/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.5 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Philipp Bärfuss | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | 0d | Original Estimate: | 0d |
| Issue Links: |
|
||||||||||
| Sub-Tasks: |
|
||||||||||
| 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: | |||||||||||
| Comments |
| Comment by Tobias Mattsson [ 11/May/11 ] |
|
Currently the Item.isSame(Item) doesn't work with our wrappers. The only solution I see is to apply a wrapper that can deal with wrapped arguments to its methods. This would effectively be a complete transparent layer on top of the jcr implementation where wrappers can unwrap other wrappers to do semantically correct operations. |