2.0.0.CR1 will be the next release of Seam, probably followed by 2.0.0.GA. 1.3.0.GA doesn't exist (JIRA just hasn't been updated yet).
Reassuming the version 1.3.X it has been replaced from the 2.X.X?
In the CVS repository you can already see a migration guide to Seam 2.0 written by Gavin King on June 27th. From this migration guide you get a pretty good picture about what has been changed. There is change log too, in another file. If you get successful with the "ant dist", you can see the reference manual has been modified too. If you view the history of the build.xml in the root of the Seam CVS repository, you can get a clue that the Seam team thinks that it's better to call the next release Seam 2.0....
We decided to release 1.3 as 2.0 yes.
In case someone do not want to bother accessing the CVS or having trouble accessing CVS, here is the migration guide I saw this morning. Written by Gavin King. I think this will appear in the Seam site soon, but if you desparately want to get things straight now....
Seam 2.0 Migration Guide
Before you get started with Seam2, you'll need to make a few changes to
your existing code and configuration. This process should not be too
painful - if you get stuck, just refer back to the updated Seam examples.
Supported container environments
Seam 2.0 has been tested on the following containers:
* JBoss 4.2 (it is possible to run Seam2 on JBoss 4.0.5 by upgrading JSF)
* Tomcat 6.0 (Tomcat 5.5 is not compatible with JSF 1.2)
* GlassFish V2
* OC4J 11g Technology Preview
Migration to JSF 1.2
Seam 2.0 requires JSF 1.2. We now recommend Sun's JSF RI as the most
mature JSF implementation, and this is the version that ships with
most EE 5 application servers, including JBoss 4.2. To switch to the
JSF RI, you'll need to make some changes to web.xml:
* remove the MyFaces StartupServletContextListener
* remove the Ajax4JSF filter and mappings
* rename org.jboss.seam.web.SeamFilter to
Also note that for the JSF RI, client-side state saving is not required.
You'll also need to make some changes to faces-config.xml:
* Remove the (Tranactional)SeamPhaseListener declaration
* Remove the SeamELResolver declaration, if you have one
* Change the declaration of SeamFaceletViewHandler to the standard
Since Seam 1.2, you didn't need any declarations of SeamExceptionFilter
or SeamRedirectFilter in web.xml, just a single declaration of
SeamFilter. Make sure you've already made that change.
Seam's built-in components have undergone a major reorganization
designed to organize them for easier learning, and to isolate
dependencies upon particular technologies like JSF into specific
* Persistence-related components moved to org.jboss.seam.persistence
* jBPM related components moved to org.jboss.seam.bpm
* JSF-related components moved org.jboss.seam.faces
* Servlet-related components have moved to org.jboss.seam.web
* Components related to asynchronicity moved to org.jboss.seam.async
* i18n-related components moved to org.jboss.seam.international
* The Pageflow component moved to org.jboss.seam.pageflow
* The Pages component moved to org.jboss.seam.navigation
Code which depends on these APIs will need to be changed to reflect
the new Java package names.
Annotations have also been reorganized:
* BPM-related annotations moved to org.jboss.seam.annotations.bpm
* JSF-related annotations moved to org.jboss.seam.annotations.faces
* Interceptor annotations moved to
* Annotations related to asynchronicity moved to
* @RequestParameter moved to org.jboss.seam.annotations.web
* @WebRemote moved to org.jboss.seam.annotations.remoting
* @Restrict moved to org.jboss.seam.annotations.security
* Exception handling annotations moved to
Migration of components.xml
The new packaging comes with new namespaces and new schemas for
components.xml. The namespace for components in package
And the schema is:
You'll need to update your components.xml file to reflect that chance.
Take a look at the Seam examples if you're unsure of exactly what you
need to do.
Finally, some declarations must be removed completely:
* remove <conversation-is-long-running-parameter> from <core:init/>
* remove <core:ejb/>
* remove <core:microcontainer/>
* replace <core:transaction-listener/> with
Migration to JBoss Embedded
Support for deployment to JBoss Embeddable EJB3 and JBoss Microcontainer
has been removed. Instead, the new JBoss Embedded distribution gives you
a full set of EE-compatible APIs with simplified deployment.
For testing, you need the jars in Seam's lib/ directory, together with
the bootstrap/ directory in your classpath. SeamTest will automatically
start the container. Refer to the Seam examples, or seam-gen, if you have
For Tomcat deployment, follow the instructions in the user guide. You no
longer need any special configuration or packaging for Tomcat deployments.
Note that JBoss Embedded is able to bootstrap a datasource from a -ds.xml
file, so there is no longer a need for jboss-beans.xml.
Thanks thousand guys,
I want to know this because I need the ws-bpm integration with seam...
I covet from months ;-)
In case someone do not want to bother accessing the CVS or having trouble accessing CVS, here is the migration guide I saw this morning. Written by Gavin King.
Just for your information: using the FishEye browser-based CVS access, one can always get the latest version of the migration guide (or any version of any file for that matter), without an actual CVS checkout.