From seam-commits at lists.jboss.org Tue Jan 29 10:30:43 2008 Content-Type: multipart/mixed; boundary="===============6781970084737124409==" MIME-Version: 1.0 From: seam-commits at lists.jboss.org To: seam-commits at lists.jboss.org Subject: [seam-commits] Seam SVN: r7286 - trunk/doc/reference/en/modules. Date: Tue, 29 Jan 2008 10:26:43 -0500 Message-ID: --===============6781970084737124409== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: pete.muir(a)jboss.org Date: 2008-01-29 10:26:43 -0500 (Tue, 29 Jan 2008) New Revision: 7286 Modified: trunk/doc/reference/en/modules/websphere.xml Log: A few minor changes Modified: trunk/doc/reference/en/modules/websphere.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/doc/reference/en/modules/websphere.xml 2008-01-29 15:22:12 UTC (r= ev 7285) +++ trunk/doc/reference/en/modules/websphere.xml 2008-01-29 15:26:43 UTC (r= ev 7286) @@ -57,7 +57,7 @@ Required custom properties There are a couple of Websphere custom properties that are = required for Seam integration. These properties are not needed specifi= cally - for seam, but work around some issues with Websphere. These are + for Seam, but work around some issues with Websphere. These are set following the instructions here : Setting web container custom properties @@ -147,7 +147,7 @@ change because this is not full jee5 implementation. Websphere does not support Servlet - 2.5, it required Servlet + 2.5, it requires Servlet 2.4. For this change we need to adjust the = top of the web.xml file to look like the following: @@ -161,7 +161,7 @@ xsi:schemaLocation=3D"http://java.sun.com/xml/ns/j2ee = http://java.sun.com/xml/ns/j2ee/web-app_2_4.x= sd"> ]]> - Next you have to make some changes to the EJB refe= rences + Next, er have to make some changes to the EJB refe= rences in the web.xml. These changes are what will allow Websphere to bind the EJB2 references= in the web module to the the actual EJB3 beans in the EAR @@ -220,12 +220,12 @@ org.jboss.seam.transaction.LocalEjbSynchronizations ]]> - The important changes are that there is an empty + The important change is that there is an empty local-home element for each EJB. - This is the signal to Websphere so that it will make = the - correct bindings behind the scenes between the web mo= dule - and the EJB3 beans. The ejb-link - element is simply not used. + This tells Websphere to make the correct bindings bet= ween = + the web module and the EJB3 beans. The = + ejb-link element is simply not use= d. = + @@ -235,13 +235,13 @@ For this example we will be using the default datasource that comes with Websphere. To do this chan= ge the - jta-data-source element like below= . + jta-data-source element: DefaultDatasource ]]> Then we need to adjust some of the hibernate properties. First comment out the Glassfish propertie= s. - Next you need to add/change the properties below. + Next you need to add/change the properties: = = hibernate.transaction.manager_looku= p_class - — Standard hibernate transaction + — Standard Hibernate transaction manager property for Websphere 6.X @@ -270,10 +270,8 @@ EJBContext is looked up. = = - + hibernate.dialect @@ -341,8 +339,8 @@ JSF libraries — Websphere 6.1 comes with - their own version of JSF 1.1 (Seam requires JSF 1.= 2). So - we must add these jars to our application. + its own version of JSF 1.1 (Seam requires JSF 1.2)= . So + we must add these jars to our application: jsf-api.jar @@ -357,7 +355,7 @@ Since Websphere is not a fully compliant JEE5 implementation we need to - add these expression language libraries as well: + add these EL libraries: el-api.jar @@ -378,12 +376,11 @@ the /lib of the EAR. - Then finally by removing the - log4j.jar all of the log output - from our application will be added to the Websphere - logging. Addition steps are required to fully - configure log4j and those are outside of the scope= of - this document. + Finally we remove the log4j.jar = + so that all of the log output from our application= will = + be added to the Websphere log. Additional steps ar= e = + required to fully configure log4j and those are ou= tside + of the scope of this document. = @@ -397,7 +394,7 @@ default fileset that is used to populate the jboss-seam-jee5.jar. The primary change is the addition of the - GlassfishDerbyDialect.class. + GlassfishDerbyDialect.class: = = Next we need to add the library dependencies discussed a= bove. For this add the following to bottom of the - ear.lib.extras fileset entry. + ear.lib.extras fileset entry: = = = Now all that is left is to execute the ant - archive task and your application files should be= in + archive task and the built application will be in the jee5/booking/dist directory. @@ -437,8 +434,8 @@ Deploying the application to Websphere = So now we have everything we need in place. All that is lef= t is to - deploy it - just a few steps more ;) - For that we will use Websphere's administration console. As + deploy it - just a few steps more. + For this we will use Websphere's administration console. As before there are some tricks and tips that must be followed. = The steps below are for the Websphere version stated above,= yours @@ -461,7 +458,7 @@ At the top of the Enterprise Application table select Install. Below are installation - wizard pages and what needs to done on each. + wizard pages and what needs to done on each: Preparing for the application @@ -574,7 +571,7 @@ Now that we have our application installed we need= to - make some adjustments to it before we can start it. + make some adjustments to it before we can start it: Starting from the Enterprise @@ -593,7 +590,7 @@ Change the Class loader - order combo box to say + order combo box to = Classes loaded with application class loader first. @@ -628,11 +625,11 @@ You should verify that the change you just - made has stuck. We had problems with the last + made has been remembered. We have had proble= ms with the last class loader change not taking effect - even after a restart. If the change did not take = you - will need to do it manually following these - directions + will need to do it manually, following these + directions: Open the following file in a te= xt --===============6781970084737124409==--