I guess I will try the JSF 1.2 upgrade in 4.0.4. I am still using 4.0.4 because I ran into some of my HQL queries not working with 4.0.5. I never took the time to investigate and correct this issue and my app will not deploy on 4.0.5.
I will take time to migrate to 4.2 though.
Seam CVS (examples and seam-gen) is now running happily on AS 4.2.0.CR1 - take a look at one of the examples - afaik:
* Change the listener in web.xml
* Remove el-api/el-ri for jboss-el (el-api is distributed with 4.2)
* Add commons-collections and commons-beanutils if you use a4j (best to use the version that comes with a4j for now)
I can confirm that even with a quite sizable real world application the switch to 1.2 RI went fairly seamlessly ... or would it be seamfully in this case? You get it... ;)
Forgot to mention, I am using Seam 1.2.1 with a4j / Richfaces on JBoss 4.0.5
I am using a very similar setup. So hopefully it will go that way for me.
I am mainly switching due to JBoss's direction and the lack of development with MyFaces.
What technical advantages are there with JSF 1.2 in the context of a Seam application?
Are there any tricks or new functionality that will be available now or in the future using JSF 1.2?