Help

We just finished uploading Seam 2.0.2.CR1 to SourceForge and the Maven repository - so go get it!

This release fixes around 30 bugs and updates various component libraries (Groovy 1.5, Drools 4.0.6, jfreechart 1.0.8a, RichFaces 3.1.4 and Trinidad 1.2.5).

But perhaps most exciting is that we have a brand new structure for our documentation, that brings with it a style themed on SeamFramework.org! This new structure will allow us to simply incorporate translations of the reference guide and keep them up to date.

We've already had a translation of the Seam 2.0.0.GA docs into Chinese (thanks to Xiaogang Cao, Yu Limin and their community!) and I'm looking forward to others flooding in (well, perhaps not flooding... ;-)

[Download] [Reference Documentation] [Forums] [JIRA]

6 comments:
07. Apr 2008, 20:58 CET | Link

The documentation looks great! I love the consistent look and feel and the code blocks especially appear very attractive and inviting. This is certainly a landmark moment in the maturation of this project.

ReplyQuote
10. Apr 2008, 09:20 CET | Link

I migrated my application from jboss-seam-2.0.1.GA and richfaces3.1.4 to jboss-seam-2.0.2.CR1 and richfaces3.2.0 last week.

The conversation works better, especially problems about return button are solved well!

But i can not got CHINESE characters correctly, those characters become ??????.... There is no any problem about this issue in jboss-seam-2.0.1.GA.

Detail steps: 1.input some CHINESE characters in certain page. 2.print them in session beans. Now, the console just print ?????? --------------------------------- 3.replace seam2.0.2 jars with seam2.0.1.GA jars. replace Richfaces3.2.0 jars with Richfaces 3.1.4jars. 4.This probles disappear.

I searched related topics about UTF-8, i think there may be something wrong with seam2.0.2CR1.

Now, i will try seam2.0.2 and richfaces3.1.4. If this composition DOES work, then the problem must be cause by richfaces3.2.0. If this composition DOES NOT work, then the problem must be cause by seam2.0.2.RC1

10. Apr 2008, 10:36 CET | Link
it's caused by Richfaces3.2.0

I rechecked this problem and found that this problem is cause by Richfaces3.2.0.

I changed back to Richfaces3.1.4 and seam2.0.2.CR1, all works well.

seam2.0.2.CR1 works better!!! thanks to Seam Team. I love seam!!!

19. Apr 2008, 19:01 CET | Link
zhaoyun

that true

16. Apr 2008, 09:57 CET | Link
ANDYHAN

That is a big bug in Richfaces 3.2.0.GA, and will be fixed in version 3.2.0.SR1

17. Apr 2008, 07:15 CET | Link
sriramsudheer

Just wondering what setting do i need to change to migrate from seam2.0.1GA to seam2.0.2.CR1

Post Comment