[seam-issues] [JBoss JIRA] Moved: (SEAMCONFIG-27) support collection and array virtual fields

Jason Porter (JIRA) jira-events at lists.jboss.org
Tue Apr 19 17:12:46 EDT 2011


     [ https://issues.jboss.org/browse/SEAMCONFIG-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Porter moved SEAMXML-22 to SEAMCONFIG-27:
-----------------------------------------------

              Project: Seam Config (fixed)  (was: Seam Config)
                  Key: SEAMCONFIG-27  (was: SEAMXML-22)
             Workflow: Seam Workflow  (was: GIT Pull Request workflow )
    Affects Version/s:     (was: 3.0.0.Beta1)
        Fix Version/s:     (was: Future)


> support collection and array virtual fields
> -------------------------------------------
>
>                 Key: SEAMCONFIG-27
>                 URL: https://issues.jboss.org/browse/SEAMCONFIG-27
>             Project: Seam Config (fixed)
>          Issue Type: Feature Request
>            Reporter: Dan Allen
>            Assignee: Stuart Douglas
>
> Add support for defining virtual fields that are of type collection or array. This should work already in theory, but no matter what I tried, I got errors, so it may simply be broken. There is also one piece missing. There needs to be a way to specify the collection type parameter (item type). I'm envisioning something like this:
> <List>
>    <Integer/> <-- defines item type
>    <app:DiceValues/>
>    <value>1</value>
>    <value>2</value> 
>    <value>3</value>
>    <value>4</value>
>    <value>5</value>
>    <value>6</value>  
> </List>
> defines the virtual field:
> @DiceValues
> List<Integer> anonymous;
> In the same way, we should support virtual arrays:
> <array>
>    <Integer/>
>    <app:DiceValues/>
>    <value>1</value>
>    <value>2</value> 
>    <value>3</value>
>    <value>4</value>
>    <value>5</value>
>    <value>6</value>  
> </array>
> producing:
> @DiceValues
> Integer[] anonymous;
> The nested element for the type is a bit awkward, though (I suggested it because it's currently how array's are typed). It would make more sense to use an attribute here:
> <List itemType="java.lang.Integer">
>    ...
> </List>
> Also, a way to control the implementation type:
> <List type="java.util.ArrayList" itemType="java.lang.Integer">
>    ...
> </List>
> Once working, there definitely needs to be an example (or two) added to the documentation. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list