[MAGNOLIA-1474] Allow basic support for reference properties Created: 20/Apr/07 Updated: 23/Jan/13 Resolved: 31/May/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 3.1 M2 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| 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 |
|
NodeData should be able to return a Content instance if the property is of type REFERENCE. |
| Comments |
| Comment by Magnolia International [ 20/Apr/07 ] |
|
added NodeData.getReferencedContent(), which will throw a RepositoryException (actually a ValueFormatException9, as per the jcr api, if the property is not of type REFERENCE. to check: how this behaves with activation (since activation might try to create references to nodes that haven't been activated/imported yet) |
| Comment by Philipp Bracher [ 31/May/07 ] |
|
I added support for pathes and uuids as String values. If the value is a path or uuid a call to getReferencedContent() will work accordingly. Activation: because of the mentioned issue we use normaly uuids stored as strings (no integrity checks). |