[MAGNOLIA-1551] pages: use content2bean Created: 24/May/07 Updated: 23/Jan/13 Resolved: 16/Aug/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | None |
| Fix Version/s: | 3.5 RC1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | 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 |
|
Create a properties map based on the node (using content2bean). Set this properties on freshly created pages. This allows having configured pages like defining the selectable repositories in the acl selecting page |
| Comments |
| Comment by Philipp Bracher [ 16/Aug/07 ] |
|
When we create the properties map we can not resolve types by reflection because there is no parent bean/class. |