-
1. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
jsoye Jun 14, 2011 10:21 AM (in response to miguelz)Hi,
I'm currently converting a Seam 2 application to Seam 3. Once you start, you'll really like CDI (The Weld Reference documentation is a great introduction, I think). As some modules, like the Mail Module, aren't ready yet, you might consider just writing them in Java EE 6 (Java Mail API, say), and adding in the Seam module and converting over at a later stage, when it's completed and there's documentation.But as for gaining productivity; you might be disappointed at the moment. You're not going to get the number of examples you have in Seam 2 at present, so if you're on a tight deadline, I wouldn't consider using Seam 3 to be a safe move right now - more for fear of the unknown, than anything else. Things might work, or might have sufficient documentation, but if they don't, how long will it take to resolve? Would it require a JIRA post, etc?
My biggest showstopper, and consequently it would be my number 1 priority, would be to get hot deployment / incremental hot deployment incorporated into a Maven plugin. Developing without it is just painful, and ultimately may be the reason why I just postpone this until next year. I'd guess my friends in PHP land would have their projects comfortably completed (stress-free) before I've even got a build going (slight exaggeration, maybe ;-D).
-
2. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
tandraschko Jun 14, 2011 10:29 AM (in response to miguelz)I would not migrate to seam 3.
It's still buggy.
1) Seam Persistence fails in clustered envorionment (workaround available)
2) org.jobss.weld.beans.ManagedBean is not serializable - You can not use @ViewScoped for JSF beans (which is really a showstopper for me!!!)
3) Seam (Faces) does not work with OWB (i thought it could be a workaround for 2.) -
3. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
jsoye Jun 14, 2011 11:33 AM (in response to miguelz)
Thomas Andraschko wrote on Jun 14, 2011 10:29:
2) org.jobss.weld.beans.ManagedBean is not serializable - You can not use @ViewScoped for JSF beans (which is really a showstopper for me!!!)Hi Thomas, Have a look at possible solutions to your problem here, in particular the 5th post from Steven Verborgh.
-
4. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
tandraschko Jun 14, 2011 11:59 AM (in response to miguelz)Hi,
AFAIK the @ViewScoped support is already in Seam Faces?
If i use the @ViewScoped on a bean, it will throw an exception because org.jobss.weld.beans.ManagedBean is not serializable. (Weld 1.1.1)
It should be the same problem as: https://issues.apache.org/jira/browse/EXTCDI-118.
I read on a mailinglist that it would be fixed with WELD 1.2.Beta1 but it isn't available!? -
5. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
jsoye Jun 14, 2011 12:16 PM (in response to miguelz)You're right. It came in the Seam 3.0.0.Alpha2 release. Sorry for the false hope. Roll on WELD 1.2.Beta1 so. Guess who hasn't been using @ViewScoped?
-
6. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
bleathem Jun 14, 2011 2:08 PM (in response to miguelz)I've been using @ViewScoped for a long time now, without any trouble.
Just make your @ViewScoped beans implement Serializable, and do not use the @ManagedBean annotation (used @Named instead).
-
7. Re: Migration Nightmare: Seam 2 -> 3, JSF 1 -> 2, Richfaces 3 -> 4
tandraschko Jun 14, 2011 2:28 PM (in response to miguelz)Which weld version do you use?
I used 1.1.1 and 1.1.2-SNAPSHOT