[
https://issues.jboss.org/browse/SEAMCONFIG-29?page=com.atlassian.jira.plu...
]
Jason Porter moved SEAMXML-25 to SEAMCONFIG-29:
-----------------------------------------------
Project: Seam Config (fixed) (was: Seam Config)
Key: SEAMCONFIG-29 (was: SEAMXML-25)
Workflow: Seam Workflow (was: GIT Pull Request workflow )
Affects Version/s: (was: 3.0.0.Beta1)
Component/s: XML Provider
(was: XML Provider)
Fix Version/s: (was: Future)
Introduce s:values tag
----------------------
Key: SEAMCONFIG-29
URL:
https://issues.jboss.org/browse/SEAMCONFIG-29
Project: Seam Config (fixed)
Issue Type: Feature Request
Components: XML Provider
Reporter: Jozef Hartinger
Assignee: Stuart Douglas
Priority: Minor
Currently, it is quite verbose to populate a collection with configured object instances
using the XML module.
For example:
Foo is a class having a collection (bars) of Bars
<e:Foo>
<e:bars>
<s:value>
<e:Bar id="1"/>
</s:value>
<s:value>
<e:Bar id="2"/>
</s:value>
<s:value>
<e:Bar id="3"/>
</s:value>
<s:value>
<e:Bar id="4"/>
</s:value>
</e:bars>
</e:Foo>
If the s:values tag is introduced, it'll make the configuration less verbose
<e:Foo>
<e:bars>
<s:values>
<e:Bar id="1"/>
<e:Bar id="2"/>
<e:Bar id="3"/>
<e:Bar id="4"/>
</s:values>
</e:bars>
</e:Foo>
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira