4.3.8. Review a Summary of the Changes Made When Migrating the Seam 2.2 Booking Application

Although it would be much more efficient to determine dependencies in advance and add the implicit dependencies in one step, this exercise shows how problems appear in the log and provides some information on how to debug and resolve them. The following is a summary of changes made to the application when migrating it to JBoss EAP 6.

Important

Applications that use Hibernate directly with Seam 2.2 may use a version of Hibernate 3 packaged inside the application. Hibernate 4, which is provided through the org.hibernate module of JBoss EAP 6, is not supported by Seam 2.2. This example is intended to help you get your application running on JBoss EAP 6 as a first step. Please be aware that packaging Hibernate 3 with a Seam 2.2 application is not a supported configuration.
  1. You created a jboss-deployment-structure.xml file in the EAR's META-INF/ directory. You added <dependencies> and <exclusions> to resolve ClassNotFoundExceptions. This file contains the following data: 
    <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
  <deployment>
  	  <dependencies>
	      <module name="javax.faces.api" slot="1.2" export="true"/>
	      <module name="com.sun.jsf-impl" slot="1.2" export="true"/>
	      <module name="org.apache.commons.logging" export="true"/>
    	      <module name="org.dom4j" export="true"/>
	      <module name="org.apache.commons.collections" export="true"/>
	    </dependencies>
  </deployment>
  <sub-deployment name="jboss-seam-booking.war">
  	<exclusions>
	      <module name="javax.faces.api" slot="main"/>
	      <module name="com.sun.jsf-impl" slot="main"/>
	    </exclusions>
	    <dependencies>
	      <module name="javax.faces.api" slot="1.2"/>
	      <module name="com.sun.jsf-impl" slot="1.2"/>
	    </dependencies>
  </sub-deployment>
</jboss-deployment-structure>
  2. You copied the following JARs from the EAP5_HOME/jboss-eap-5.X/seam/lib/ directory (replace 5.X with the version of EAP 5 that you are migrating from) to the jboss-seam-booking.ear/lib/ directory to resolve ClassNotFoundExceptions:
    • hibernate-core.jar
    • hibernate-validator.jar
  3. You modified the jboss-seam-booking.jar/META-INF/persistence.xml file as follows.
    1. You changed the jta-data-source element to use the Example database that ships with JBoss EAP 6: 
      <!-- <jta-data-source>java:/bookingDatasource</jta-data-source> -->
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
    2. You commented out the hibernate.cache.provider_class property: 
      <!-- <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/> -->
  4. You modified the WAR's lib/components.xml file to use the new JNDI bindings
    1. You replaced the core:init existing element as follows: 
      <!-- <core:init jndi-pattern="jboss-seam-booking/#{ejbName}/local" debug="true" distributable="false"/> -->
<core:init jndi-pattern="java:app/jboss-seam-booking.jar/#{ejbName}" debug="true" distributable="false"/>
    2. You added component elements for the "EjbSynchronizations" and "TimerServiceDispatcher" JNDI bindings 
      <component class="org.jboss.seam.transaction.EjbSynchronizations" jndi-name="java:app/jboss-seam/EjbSynchronizations"/>
 <component class="org.jboss.seam.async.TimerServiceDispatcher" jndi-name="java:app/jboss-seam/TimerServiceDispatcher"/>
Report a bug