FYI: Seam 2 CR1 has been released

[smithbstl]

I have been following Jira and the last bug was closed this morning. I just checked the download page and Seam 2 CR1 has been released.

Yea!

http://labs.jboss.com/jbossseam/download/index.html

[amitev]

Great job!

[mgrouch]

Looks like it gained some weight

120 MB

vs

73 MB in 1.2.1.GA

[pmuir]

You guys are on the ball - we can't keep up!

[norman.richards]

It takes a little time to get everything in place, but yes we just finished the release process. Please report any issues you find with it so we can move towards making the final release.

[gbc1]

Hello,

well done! Is there some kind of migration guide from seam2 Beta1 to cr1?

How to best upgrade an existing project?

Greetz GHad

[norman.richards]

I'm not aware of any breaking changes. You should be able to simply update to the latest JARs.

[mgrouch]

Which version of facelets doesn't come with?
Is ui:insert for source tags fixed?
Thanks,
Congrats with RC!

[hafidzmalik]

Invalid url inside new jboss-seam-2.0.0.CR1\readme.txt

* Read the online FAQ http://www.jboss.com/products/seam/faq

should be
* Read the online FAQ http://labs.jboss.com/jbossseam/faq

[pmuir]

It comes with facelets 1.1.13 draft - the source tags fix is not included with this. You'll need to build a facelets jar from CVS if you want this fix. As soon as facelets release a new version we will update.

[gbc1]

Already noticed one bigger change and some small ones from Beta1 to CR1 for existing projects:

- ajax4jsf.jar must be exlcuded from the project (because now merged with richfaces)
- JBoss warns me: WARN [SkinFactoryImpl] Init parameter for a skin name changed to org.richfaces.SKIN
- So needs change in web.xml
- Do I need to edit: org.ajax4jsf.VIEW_HANDLERS?
- Libraries in lib folder needs to be updated (of course)
- application.xml needs update on same jars as the version changed

So far, hope this helps someone,

Greetz GHad

[wise_guybg]

[e-mail]: I would suggest you go by the Application 5 specification and instead of describing each jar file in the application.xml, you put them all in /lib inside your EAR.

[e-mail]: I want to ask if JSTL library should be updated. Version 1.1.0 is provided while there exists jstl-1.1.2.jar:
http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html
http://jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi

[gbc1]

"wise_guybg" wrote:
[e-mail]: I would suggest you go by the Application 5 specification and instead of describing each jar file in the application.xml, you put them all in /lib inside your EAR.

Does this work with jars containing seam components (wrote a little framework) as well? By now we're using MyEclipse w/ exploded deploy. Our actual version does not support deployment into /lib (at least we didn't try by now, but this is on our features wishlist since JBoss 4.2 has been released)

Thanks for info!

Greetz GHad

[wise_guybg]

Yes, it's JBoss 4.2 that supports it. You can put all your library jars in the /lib directory instead of root and skip declaring them in application.xml. It doesn't matter if you deploy from an exploded directory.

[igx89]

How long do we have to wait until CR1 makes it into a Maven repository? That'd be incredibly helpful...