10 Replies Latest reply on Aug 28, 2007 9:48 AM by fhh

    Seam 2.0: Why does @Datamodel require a setter?



      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.

      Is this change of behaviour intended?



      P.S.: Does anybody know why deployment exceptions are swalloed?