[MAGNOLIA-3838] As we're moving away from Content-API we have to create a Node2Bean mechanism replacing the existing Content2Bean. Created: 15/Sep/11 Updated: 20/Feb/13 Resolved: 04/Oct/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | content2bean, core |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Description |
|
Content2Bean should get deprecated - as all the other Content-API types. It's implementation should internally retrieve the JCR-Node from the Content and then delegate to Node2Bean mechanism. |