[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1868) @DataModel should not require a setter

Pete Muir (JIRA) jira-events at lists.jboss.org
Sun Dec 2 12:25:13 EST 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-1868?page=all ]

Pete Muir closed JBSEAM-1868.
-----------------------------


> @DataModel should not require a setter
> --------------------------------------
>
>                 Key: JBSEAM-1868
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1868
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>         Environment: SEAM 2.0.BETA1
>            Reporter: Felix Ho?feld
>         Assigned To: Pete Muir
>             Fix For: 2.0.0.CR1
>
>
> This patch http://lists.jboss.org/pipermail/jboss-cvs-commits/2007-August/039852.html
> requires all methods annotated with @Datamodels to have a corresponding setter.
> This makes the Seam 2.0 migration much harder than necessary. My project has lots of lists that are created on the fly when the get-Method is called. So these are really readonly. Seam 2.0 will require to add empty setters to all these components.
> IMHO a setter should not even be required when susing @DataModelSelection. The datamodel should be available from the context it was outjected to. Pre Seam 2.0 this was not required so this is a clear regression to me. On the other hand adding emty setters is not that hard...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list