[MAGNOLIA-3160] node2bean should allow to specify implementations for Collections Created: 22/Mar/10 Updated: 11/Feb/13 Resolved: 16/Oct/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | content2bean |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Jaroslav Simak |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
Currently, all Map and Collection properties are populated via a LinkedHashMap. While this is a good default, content2bean should respect the cases where a specific implementation is mandated by the configuration. (i.e specifying a property class=MyCollectionImplementation) |
| Comments |
| Comment by Magnolia International [ 22/Mar/10 ] |
|
See Content2BeanTest#testCanSpecifySpecificCollectionImplementation() |