Seam SVN: r7294 - in trunk/seam-gen: resources/WEB-INF and 1 other directory.
by seam-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2008-01-29 17:32:15 -0500 (Tue, 29 Jan 2008)
New Revision: 7294
Modified:
trunk/seam-gen/icefaces/resources/WEB-INF/components-war.xml
trunk/seam-gen/icefaces/resources/WEB-INF/components.xml
trunk/seam-gen/resources/WEB-INF/components-war.xml
trunk/seam-gen/resources/WEB-INF/components.xml
Log:
set the parent-conversation-id-parameter to match convention with the conversation-id-parameter
Modified: trunk/seam-gen/icefaces/resources/WEB-INF/components-war.xml
===================================================================
--- trunk/seam-gen/icefaces/resources/WEB-INF/components-war.xml 2008-01-29 19:51:44 UTC (rev 7293)
+++ trunk/seam-gen/icefaces/resources/WEB-INF/components-war.xml 2008-01-29 22:32:15 UTC (rev 7294)
@@ -20,7 +20,8 @@
<core:manager concurrent-request-timeout="500"
conversation-timeout="120000"
- conversation-id-parameter="cid"/>
+ conversation-id-parameter="cid"
+ parent-conversation-id-parameter="pid"/>
<persistence:managed-persistence-context name="entityManager"
auto-create="true"
Modified: trunk/seam-gen/icefaces/resources/WEB-INF/components.xml
===================================================================
--- trunk/seam-gen/icefaces/resources/WEB-INF/components.xml 2008-01-29 19:51:44 UTC (rev 7293)
+++ trunk/seam-gen/icefaces/resources/WEB-INF/components.xml 2008-01-29 22:32:15 UTC (rev 7294)
@@ -20,7 +20,8 @@
<core:manager concurrent-request-timeout="500"
conversation-timeout="120000"
- conversation-id-parameter="cid"/>
+ conversation-id-parameter="cid"
+ parent-conversation-id-parameter="pid"/>
<persistence:managed-persistence-context name="entityManager"
auto-create="true"
@@ -50,4 +51,4 @@
</bpm:jbpm>
-->
-</components>
\ No newline at end of file
+</components>
Modified: trunk/seam-gen/resources/WEB-INF/components-war.xml
===================================================================
--- trunk/seam-gen/resources/WEB-INF/components-war.xml 2008-01-29 19:51:44 UTC (rev 7293)
+++ trunk/seam-gen/resources/WEB-INF/components-war.xml 2008-01-29 22:32:15 UTC (rev 7294)
@@ -20,7 +20,8 @@
<core:manager concurrent-request-timeout="500"
conversation-timeout="120000"
- conversation-id-parameter="cid"/>
+ conversation-id-parameter="cid"
+ parent-conversation-id-parameter="pid"/>
<persistence:managed-persistence-context name="entityManager"
auto-create="true"
Modified: trunk/seam-gen/resources/WEB-INF/components.xml
===================================================================
--- trunk/seam-gen/resources/WEB-INF/components.xml 2008-01-29 19:51:44 UTC (rev 7293)
+++ trunk/seam-gen/resources/WEB-INF/components.xml 2008-01-29 22:32:15 UTC (rev 7294)
@@ -20,7 +20,8 @@
<core:manager concurrent-request-timeout="500"
conversation-timeout="120000"
- conversation-id-parameter="cid"/>
+ conversation-id-parameter="cid"
+ parent-conversation-id-parameter="pid"/>
<persistence:managed-persistence-context name="entityManager"
auto-create="true"
16 years, 11 months
- 1
- 0
Seam SVN: r7293 - tags.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-01-29 14:51:44 -0500 (Tue, 29 Jan 2008)
New Revision: 7293
Added:
tags/JBoss_Seam_2_0_1_GA/
Log:
2.0.1.GA
Copied: tags/JBoss_Seam_2_0_1_GA (from rev 7292, branches/Seam_2_0)
16 years, 11 months
- 1
- 0
Seam SVN: r7292 - in trunk/seam-gen: view and 1 other directory.
by seam-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2008-01-29 14:33:50 -0500 (Tue, 29 Jan 2008)
New Revision: 7292
Modified:
trunk/seam-gen/icefaces/view/edit.xhtml
trunk/seam-gen/icefaces/view/edit.xhtml.ftl
trunk/seam-gen/view/edit.xhtml
trunk/seam-gen/view/edit.xhtml.ftl
Log:
add immediate="true" to Delete buttons so that validation is bypassed (no need to validate what we are deleting)
Modified: trunk/seam-gen/icefaces/view/edit.xhtml
===================================================================
--- trunk/seam-gen/icefaces/view/edit.xhtml 2008-01-29 19:28:48 UTC (rev 7291)
+++ trunk/seam-gen/icefaces/view/edit.xhtml 2008-01-29 19:33:50 UTC (rev 7292)
@@ -43,6 +43,7 @@
<h:commandButton id="edit@homeName@delete"
value="Delete"
action="#{@homeName@.remove}"
+ immediate="true"
rendered="#{@homeName@.managed}"/>
<s:button propagation="end"
id="edit@homeName@done"
Modified: trunk/seam-gen/icefaces/view/edit.xhtml.ftl
===================================================================
--- trunk/seam-gen/icefaces/view/edit.xhtml.ftl 2008-01-29 19:28:48 UTC (rev 7291)
+++ trunk/seam-gen/icefaces/view/edit.xhtml.ftl 2008-01-29 19:33:50 UTC (rev 7292)
@@ -55,6 +55,7 @@
<h:commandButton id="delete${homeName}"
value="Delete"
action="${'#'}{${homeName}.remove}"
+ immediate="true"
rendered="${'#'}{${homeName}.managed}"/>
<s:button id="done${homeName}"
Modified: trunk/seam-gen/view/edit.xhtml
===================================================================
--- trunk/seam-gen/view/edit.xhtml 2008-01-29 19:28:48 UTC (rev 7291)
+++ trunk/seam-gen/view/edit.xhtml 2008-01-29 19:33:50 UTC (rev 7292)
@@ -39,6 +39,7 @@
<h:commandButton id="delete"
value="Delete"
action="#{@homeName@.remove}"
+ immediate="true"
rendered="#{@homeName@.managed}"/>
<s:button propagation="end"
id="done"
Modified: trunk/seam-gen/view/edit.xhtml.ftl
===================================================================
--- trunk/seam-gen/view/edit.xhtml.ftl 2008-01-29 19:28:48 UTC (rev 7291)
+++ trunk/seam-gen/view/edit.xhtml.ftl 2008-01-29 19:33:50 UTC (rev 7292)
@@ -50,6 +50,7 @@
<h:commandButton id="delete"
value="Delete"
action="${'#'}{${homeName}.remove}"
+ immediate="true"
rendered="${'#'}{${homeName}.managed}"/>
<s:button id="done"
16 years, 11 months
- 1
- 0
Seam SVN: r7291 - in branches/Seam_2_0: build and 1 other directory.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-01-29 14:28:48 -0500 (Tue, 29 Jan 2008)
New Revision: 7291
Modified:
branches/Seam_2_0/build/default.build.properties
branches/Seam_2_0/changelog.txt
branches/Seam_2_0/readme.txt
Log:
prep for GA
Modified: branches/Seam_2_0/build/default.build.properties
===================================================================
--- branches/Seam_2_0/build/default.build.properties 2008-01-29 19:14:16 UTC (rev 7290)
+++ branches/Seam_2_0/build/default.build.properties 2008-01-29 19:28:48 UTC (rev 7291)
@@ -8,7 +8,7 @@
major.version 2
minor.version .0
patchlevel .1
-qualifier -SNAPSHOT
+qualifier .GA
#
# Other program locations
# -----------------------
Modified: branches/Seam_2_0/changelog.txt
===================================================================
--- branches/Seam_2_0/changelog.txt 2008-01-29 19:14:16 UTC (rev 7290)
+++ branches/Seam_2_0/changelog.txt 2008-01-29 19:28:48 UTC (rev 7291)
@@ -1,6 +1,33 @@
JBoss Seam Changelog
====================
+Release Notes - JBoss Seam - Version 2.0.1.GA
+
+** Bug
+ * [JBSEAM-1034] - Usage of jBPM core:process-definitions needs clarification
+ * [JBSEAM-1103] - Deploying Seam example app into /trunk causes ZipException
+ * [JBSEAM-1522] - @Intercept is gone but still documented
+ * [JBSEAM-2243] - org.jboss.seam.persistence.HibernateSessionProxy does not implement org.hibernate.event.EventSource
+ * [JBSEAM-2373] - Seam-gen makes /Applications/jboss-4.2.2.GA the even when JBoss home is specified as C:/jboss-4.2.1.GA
+ * [JBSEAM-2516] - Hibernate Search integration leads to CCE when using Search.createEMF
+ * [JBSEAM-2526] - org.jboss.seam.core.SeamResourceBundle::getKeys()
+ * [JBSEAM-2527] - <s:convertEntity /> doesn't detect custom object added through external hibernate.cfg.xml
+ * [JBSEAM-2532] - org.jboss.seam.pdf.DocumentData needs to be serializable
+ * [JBSEAM-2533] - Invalid security message keys in documentation
+ * [JBSEAM-2538] - Incorrect escaping of paths in seam-gen generated build.properties
+ * [JBSEAM-2543] - Typos in Seam documentation
+
+** Feature Request
+ * [JBSEAM-619] - Make the booking work on WAS EJB3 Preview
+
+** Task
+ * [JBSEAM-2151] - Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples
+ * [JBSEAM-2392] - document p:html
+ * [JBSEAM-2483] - Deploy Seam applications to Websphere 6.1.X and create Reference guide chapter
+ * [JBSEAM-2536] - Complete Annotations for use with Seam JavaBean components in a J2EE environment section
+ * [JBSEAM-2542] - Document semantics of s:link with view and action
+
+
Release Notes - JBoss Seam - Version 2.0.1.CR2
** Bug
Modified: branches/Seam_2_0/readme.txt
===================================================================
--- branches/Seam_2_0/readme.txt 2008-01-29 19:14:16 UTC (rev 7290)
+++ branches/Seam_2_0/readme.txt 2008-01-29 19:28:48 UTC (rev 7291)
@@ -1,6 +1,6 @@
JBoss Seam - Contextual Component framework for Java EE 5
=========================================================
-version 2.0.1.CR2, January 2008
+version 2.0.1.GA, January 2008
This software is distributed under the terms of the FSF Lesser Gnu
Public License (see lgpl.txt).
16 years, 11 months
- 1
- 0
Seam SVN: r7290 - in branches/Seam_2_0/seam-gen: view and 1 other directory.
by seam-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2008-01-29 14:14:16 -0500 (Tue, 29 Jan 2008)
New Revision: 7290
Modified:
branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml
branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml.ftl
branches/Seam_2_0/seam-gen/view/edit.xhtml
branches/Seam_2_0/seam-gen/view/edit.xhtml.ftl
Log:
add immediate="true" to Delete buttons so that validation is bypassed (no need to validate what we are deleting)
Modified: branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml
===================================================================
--- branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml 2008-01-29 16:25:13 UTC (rev 7289)
+++ branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml 2008-01-29 19:14:16 UTC (rev 7290)
@@ -43,6 +43,7 @@
<h:commandButton id="edit@homeName@delete"
value="Delete"
action="#{@homeName@.remove}"
+ immediate="true"
rendered="#{@homeName@.managed}"/>
<s:button propagation="end"
id="edit@homeName@done"
Modified: branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml.ftl
===================================================================
--- branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml.ftl 2008-01-29 16:25:13 UTC (rev 7289)
+++ branches/Seam_2_0/seam-gen/icefaces/view/edit.xhtml.ftl 2008-01-29 19:14:16 UTC (rev 7290)
@@ -55,6 +55,7 @@
<h:commandButton id="delete${homeName}"
value="Delete"
action="${'#'}{${homeName}.remove}"
+ immediate="true"
rendered="${'#'}{${homeName}.managed}"/>
<s:button id="done${homeName}"
Modified: branches/Seam_2_0/seam-gen/view/edit.xhtml
===================================================================
--- branches/Seam_2_0/seam-gen/view/edit.xhtml 2008-01-29 16:25:13 UTC (rev 7289)
+++ branches/Seam_2_0/seam-gen/view/edit.xhtml 2008-01-29 19:14:16 UTC (rev 7290)
@@ -39,6 +39,7 @@
<h:commandButton id="delete"
value="Delete"
action="#{@homeName@.remove}"
+ immediate="true"
rendered="#{@homeName@.managed}"/>
<s:button propagation="end"
id="done"
Modified: branches/Seam_2_0/seam-gen/view/edit.xhtml.ftl
===================================================================
--- branches/Seam_2_0/seam-gen/view/edit.xhtml.ftl 2008-01-29 16:25:13 UTC (rev 7289)
+++ branches/Seam_2_0/seam-gen/view/edit.xhtml.ftl 2008-01-29 19:14:16 UTC (rev 7290)
@@ -50,6 +50,7 @@
<h:commandButton id="delete"
value="Delete"
action="${'#'}{${homeName}.remove}"
+ immediate="true"
rendered="${'#'}{${homeName}.managed}"/>
<s:button id="done"
16 years, 11 months
- 1
- 0
Seam SVN: r7289 - trunk/doc/reference/en/modules.
by seam-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2008-01-29 11:25:13 -0500 (Tue, 29 Jan 2008)
New Revision: 7289
Modified:
trunk/doc/reference/en/modules/websphere.xml
Log:
updated with seam-gen section
Modified: trunk/doc/reference/en/modules/websphere.xml
===================================================================
--- trunk/doc/reference/en/modules/websphere.xml 2008-01-29 16:17:05 UTC (rev 7288)
+++ trunk/doc/reference/en/modules/websphere.xml 2008-01-29 16:25:13 UTC (rev 7289)
@@ -51,6 +51,13 @@
profile with the EJB3 feature pack enabled, or augment one of your
existing ones. This can also be done after the installation
by running the profile managment tool.</para>
+ <note>
+ <title>A note about restarting the server</title>
+ <para>There are times that restarting the server will be required after
+ deploying or changes the examples in this chapter. Its does not seem
+ like every change requires a restart. If you get errors or exceptions
+ after modifing a property or deploying an application try to restart
+ the server. </para> </note>
</section>
<section>
@@ -161,7 +168,7 @@
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
]]></programlisting>
- <para>Next, er have to make some changes to the EJB references
+ <para>Next, we have to make some changes to the EJB references
in the <literal>web.xml</literal>. 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
@@ -940,4 +947,564 @@
</section>
+ <section>
+ <title>Deploying an application created using
+ <literal>seam-gen</literal> on Websphere 6.1.0.13</title>
+
+ <para><literal>seam-gen</literal> is a very useful tool for developers
+ to quickly get an application up and running, and provides a foundation
+ to add your own functionality. Out of box <literal>seam-gen</literal>
+ will produce applications configured to run on JBoss AS. These
+ instructions will show the steps needed to get it to run on Websphere.
+ As stated above in <xref linkend="jee5-websphere-section"/> there
+ are some tricky changes needed to get an EJB3 application running. This
+ section will take you through the exact steps.</para>
+
+ <para>The first step is setting up <literal>seam-gen</literal> to
+ construct the base project. There are several choices made below,
+ specifically the datasource and hibernate values that we will adjust
+ once the project is created.</para>
+
+
+ <programlisting><![CDATA[
+./seam setup
+Buildfile: build.xml
+
+init:
+
+setup:
+ [echo] Welcome to seam-gen :-)
+ [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]
+/home/jbalunas/workspace
+ [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]
+/home/jbalunas/jboss/jboss-4.2.2.GA
+ [input] Enter the project name [myproject] [myproject]
+websphere_example
+ [echo] Accepted project name as: websphere_example
+ [input] Do you want to use ICEFaces instead of RichFaces [n] (y, [n], )
+
+ [input] skipping input as property icefaces.home.new has already been set.
+ [input] Select a RichFaces skin [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)
+
+ [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )
+
+ [input] Enter the Java package name for your session beans [com.mydomain.websphere_example] [com.mydomain.websphere_example]
+org.jboss.seam.tutorial.websphere.action
+ [input] Enter the Java package name for your entity beans [org.jboss.seam.tutorial.websphere.action] [org.jboss.seam.tutorial.websphere.action]
+org.jboss.seam.tutorial.websphere.model
+ [input] Enter the Java package name for your test cases [org.jboss.seam.tutorial.websphere.action.test] [org.jboss.seam.tutorial.websphere.action.test]
+org.jboss.seam.tutorial.websphere.test
+ [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)
+
+ [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]
+
+ [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]
+
+ [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] [org.hsqldb.jdbcDriver]
+
+ [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.]
+
+ [input] Enter database username [sa] [sa]
+
+ [input] Enter database password [] []
+
+ [input] Enter the database schema name (it is OK to leave this blank) [] []
+
+ [input] Enter the database catalog name (it is OK to leave this blank) [] []
+
+ [input] Are you working with tables that already exist in the database? [n] (y, [n], )
+
+ [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )
+
+[propertyfile] Creating new property file: /rhdev/projects/jboss-seam/svn-seam_2_0/jboss-seam-2_0/seam-gen/build.properties
+ [echo] Installing JDBC driver jar to JBoss server
+ [copy] Copying 1 file to /home/jbalunas/jboss/jboss-4.2.2.GA/server/default/lib
+ [echo] Type 'seam create-project' to create the new project
+
+BUILD SUCCESSFUL
+Total time: 3 minutes 5 seconds]]></programlisting>
+
+ <para> Type <literal>./seam new-project</literal> to create your
+ project and <literal>cd
+ /home/jbalunas/workspace/websphere_example</literal> to the
+ newly created structure. </para>
+
+ </section>
+ <section>
+ <title>Changes needed for deployment to Websphere</title>
+ <para>We now need to make some changes to the generated project.</para>
+ <section>
+ <title>Configuration file changes</title>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <literal>resources/META-INF/persistence-dev.xml</literal>
+ </term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Alter the
+ <literal>jta-data-source</literal> to be
+ <literal>DefaultDatasource</literal>. We are
+ going to be using the integrated Websphere
+ DB.</para>
+ </listitem>
+ <listitem>
+ <para> Add or change the properties below.
+ These are described in detail at <xref
+ linkend="jee5-websphere-section"/>:
+ </para>
+
+ <programlisting><![CDATA[
+<property name="hibernate.dialect" value="GlassfishDerbyDialect"/>
+<property name="hibernate.hbm2ddl.auto" value="update"/>
+<property name="hibernate.show_sql" value="true"/>
+<property name="hibernate.format_sql" value="true"/>
+<property name="hibernate.cache.provider_class"
+ value="org.hibernate.cache.HashtableCacheProvider"/>
+<property name="hibernate.transaction.manager_lookup_class"
+ value="org.hibernate.transaction.WebSphereExtendedJTATransactionLookup"/>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> Remove the JBoss AS specific method of exposing
+ the EntityManagerFactory: </para>
+
+ <programlisting><![CDATA[<property
+ name="jboss.entity.manager.factory.jndi.name"
+ value="java:/websphere_exampleEntityManagerFactory">]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> You'll need to alter
+ <literal>persistence-prod.xml</literal> as
+ well if you want to deploy to Websphere using the
+ prod profile. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/GlassfishDerbyDialect.class</literal>
+ </term>
+ <listitem>
+ <para>As with other examples we need to include this class for
+ DB support. It can be copied from the
+ <literal>jpa</literal> example into the
+ <literal>websphere_example/resources</literal>
+ directory.
+
+ <programlisting><![CDATA[
+cp $SEAM/examples/jpa/resources-websphere61/WEB-INF/classes/GlassfishDerbyDialect.class
+ ./resources]]></programlisting>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/META-INF/jboss-app.xml</literal>
+ </term>
+ <listitem>
+ <para> You can delete this file as we aren't deploying to JBoss
+ AS ( <literal>jboss-app.xml</literal> is used to enable
+ classloading isolation in JBoss AS) </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term> <literal>resources/*-ds.xml</literal>
+ </term>
+ <listitem>
+ <para> You can delete these file as we aren't deploying to
+ JBoss AS (these files define datasources in JBoss AS, we
+ are using Websphere's default datasource) </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/WEB-INF/components.xml</literal>
+ </term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Enable container managed transaction
+ integration - add the <literal>
+ <transaction:ejb-transaction />
+ </literal> component, and it's namespace
+ declaration <literal>
+ xmlns:transaction="http://jboss.com/products/seam/transaction"
+ </literal> </para>
+ </listitem>
+ <listitem>
+ <para> Alter the <literal>jndi-pattern</literal>
+ to <literal>
+ java:comp/env/websphere_example/#{ejbName}
+ </literal> </para>
+ </listitem>
+ <listitem>
+ <para>We do not need
+ <literal>managed-persistence-context</literal>
+ for this example and so can delete its
+ entry.</para>
+
+
+ <programlisting><![CDATA[
+<persistence:managed-persistence-context name="entityManager"
+ auto-create="true"
+ persistence-unit-jndi-name="java:/websphere_exampleEntityManagerFactory"/> ]]></programlisting>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term> <literal>resources/WEB-INF/web.xml</literal>
+ </term>
+ <listitem>
+ <para> Websphere does not support <literal>Servlet
+ 2.5</literal>, it required <literal>Servlet
+ 2.4</literal>. For this change we need to adjust the top of
+ the <literal>web.xml</literal> file to look like the
+ following:</para>
+
+ <programlisting><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<web-app version="2.4"
+ xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
+ ]]></programlisting>
+
+ <para>As with the <literal>jee5/booking</literal>
+ example we need to add EJB references to the web.xml. These
+ references require the empty
+ <literal>local-home</literal> to flag them for
+ Websphere to perform the proper binding.</para>
+
+
+ <programlisting><![CDATA[
+ <ejb-local-ref>
+ <ejb-ref-name>websphere_example/AuthenticatorAction</ejb-ref-name>
+ <ejb-ref-type>Session</ejb-ref-type>
+ <local-home></local-home>
+ <local>org.jboss.seam.tutorial.websphere.action.Authenticator</local>
+ </ejb-local-ref>
+
+ <ejb-local-ref>
+ <ejb-ref-name>websphere_example/EjbSynchronizations</ejb-ref-name>
+ <ejb-ref-type>Session</ejb-ref-type>
+ <local-home></local-home>
+ <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>
+ </ejb-local-ref>]]></programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section>
+ <title>Creating the <literal>AuthenticatorAction</literal>
+ EJB</title>
+ <para> We want to take the existing <literal>Authenticator</literal>
+ Seam POJO component and create an EJB3 out of it. </para>
+ <orderedlist>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Rename the class to
+ <literal>AuthenticatorAction</literal> </para>
+ </listitem>
+ <listitem>
+ <para> Add the <literal>@Stateless</literal>
+ annotation to the new
+ <literal>AuthenticatorAction</literal> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para> Create an interface called
+ <literal>Authenticator</literal> which
+ <literal>AuthenticatorAction</literal>
+ implements (EJB3 requires session beans to have a
+ local interface). Annotate the interface with
+ <literal>@Local</literal> , and add a single method
+ with same signature as the
+ <literal>authenticate</literal> in
+ <literal>AuthenticatorAction</literal> . </para>
+ </listitem>
+ </itemizedlist>
+
+
+ <programlisting><![CDATA[
+@Name("authenticator") @Stateless public class
+ AuthenticatorAction implements Authenticator {]]></programlisting>
+
+
+ <programlisting><![CDATA[
+@Local public interface Authenticator {
+ public boolean authenticate();
+}]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>We've already added its reference to the
+ <literal>web.xml</literal> file so are good to go. </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section>
+ <title>Extra jar dependencies and other changes to the
+ <literal>build.xml</literal></title>
+ <para> This application has similar requirements as the
+ <literal>jee5/booking</literal> example. </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Change the default target to
+ <literal>archive</literal> (we aren't going to cover
+ automatic deployment to Websphere).
+
+
+ <programlisting><![CDATA[
+<project name="websphere_example" default="archive" basedir=".">]]></programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Websphere looks for the drools
+ <literal>/security.drl</literal> file in the root of the
+ <literal>war</literal> file instead of the root of the
+ <literal>websphere_example.jar</literal> so we need
+ to have the <literal>build.xml</literal> move it to the
+ correct location at build time. The following must be added at
+ the top of the <literal> <target name="war"
+ depends="compile" description="Build the distribution
+ .war file"> </literal> target.
+
+ <programlisting><![CDATA[
+<copy todir="${war.dir}">
+ <fileset dir="${basedir}/resources" >
+ <include name="*.drl" />
+ </fileset>
+</copy>]]></programlisting></para>
+ </listitem>
+ <listitem>
+ <para>We need to ge the
+ <literal>GlassfishDerbyDialect.class</literal> into
+ our application jar. To do that find the
+ <literal>jar</literal> task and modify the top of it so that
+ it looks like this:
+
+
+ <programlisting><![CDATA[
+<target name="jar" depends="compile,copyclasses"
+ description="Build the distribution .jar file">
+ <copy todir="${jar.dir}">
+ <fileset dir="${basedir}/resources">
+ <include name="seam.properties" />
+ <include name="*.drl" />
+ <include name="GlassfishDerbyDialect.class" />
+ </fileset>
+ </copy>
+...]]></programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Next we need to get the
+ <literal>jboss-seam.jar</literal> into the base of the
+ <literal>EAR</literal> file. For deployment Websphere
+ requires this jar to be in both the <literal>/lib</literal>
+ directory and at the base of the <literal>EAR</literal>. You
+ must add the following to the <literal>archive</literal>
+ task: </para>
+
+
+ <programlisting><![CDATA[
+<fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+</fileset>]]></programlisting>
+ <para>So that the whole <literal>archive</literal> task looks
+ like:</para>
+
+
+ <programlisting><![CDATA[
+<target name="archive" depends="jar,war,ear"
+ description="Package the archives">
+ <jar jarfile="${dist.dir}/${project.name}.jar" basedir="${jar.dir}"/>
+ <jar jarfile="${dist.dir}/${project.name}.war" basedir="${war.dir}"/>
+ <jar jarfile="${dist.dir}/${project.name}.ear">
+ <fileset dir="${ear.dir}"/>
+ <fileset dir="${dist.dir}">
+ <include name="${project.name}.jar"/>
+ <include name="${project.name}.war"/>
+ </fileset>
+ <fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+ </fileset>
+ </jar>
+</target>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>Now we need to get extra jars into the
+ <literal>build.xml</literal>. Look for the
+ <literal><fileset dir="${basedir}"></literal> section
+ of the task below. Add the new includes at the bottom of
+ the fileset.
+ </para>
+
+
+ <programlisting><![CDATA[
+<target name="ear" description="Build the EAR">
+ <copy todir="${ear.dir}">
+ <fileset dir="${basedir}/resources">
+ <include name="*jpdl.xml" />
+ <include name="*hibernate.cfg.xml" />
+ <include name="jbpm.cfg.xml" />
+ </fileset>
+ <fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+ </fileset>
+ <fileset dir="${basedir}">
+ <include name="lib/jbpm*.jar" />
+ <include name="lib/jboss-el.jar" />
+ <include name="lib/drools-*.jar"/>
+ <include name="lib/core.jar"/>
+ <include name="lib/janino*.jar"/>
+ <include name="lib/antlr-*.jar"/>
+ <include name="lib/mvel*.jar"/>
+ <include name="lib/richfaces-api*.jar" />
+ </fileset>
+ </copy>
+ <copy todir="${ear.dir}/META-INF">
+ <fileset dir="${basedir}/resources/META-INF">
+ <include name="application.xml" />
+ <include name="jboss-app.xml" />
+ </fileset>
+ </copy>
+</target>]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Hibernate dependencies</para>
+ <programlisting><![CDATA[
+ <!-- Hibernate and deps -->
+ <include name="lib/hibernate.jar"/>
+ <include name="lib/hibernate-commons-annotations.jar"/>
+ <include name="lib/hibernate-annotations.jar"/>
+ <include name="lib/hibernate-entitymanager.jar"/>
+ <include name="lib/hibernate-validator.jar"/>
+ <include name="lib/jboss-common-core.jar" />]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>JSF dependencies. You will need to copy the
+ <literal>el-ri.jar</literal> from the
+ <literal>$SEAM/examples/jpa/lib</literal> directory.</para>
+ <programlisting><![CDATA[
+ <!-- jsf libs -->
+ <include name="lib/jsf-api.jar" />
+ <include name="lib/jsf-impl.jar" />
+ <include name="lib/el-api.jar" />
+ <include name="lib/el-ri.jar"/>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> Third party dependencies. You will need to copy the
+ <literal>jboss-archive-browsing.jar</literal> from the
+ <literal>$SEAM/examples/jpa/lib</literal> directory into the
+ the projects <literal>/lib</literal> directory. You will
+ also need to acquire the <literal>concurrent.jar</literal>
+ and place it in the same directory. You can get this from
+ any jboss distribution or just search for it.</para>
+ <programlisting><![CDATA[
+ <!-- 3rd party and supporting jars -->
+ <!--<include name="lib/log4j.jar" />-->
+ <include name="lib/javassist.jar"/>
+ <include name="lib/dom4j.jar" />
+ <include name="lib/jboss-archive-browsing.jar" />
+ <include name="lib/concurrent.jar" />
+ <include name="lib/cglib.jar"/>
+ <include name="lib/asm.jar"/>
+ <include name="lib/antlr.jar" />
+ <include name="lib/commons-logging.jar" />
+ <include name="lib/commons-collections.jar" />]]></programlisting>
+ </listitem>
+ <listitem>
+ <para><literal>jboss-seam.jar</literal> - this is needed in
+ both the <literal>ear</literal> base and
+ <literal>/lib</literal>
+ directory.</para>
+ <programlisting><![CDATA[
+ <!-- seam jar -->
+ <include name="lib/jboss-seam.jar" />]]></programlisting>
+ </listitem>
+ </itemizedlist>
+
+ <para>You should end up with something like:</para>
+ <programlisting><![CDATA[
+<fileset dir="${basedir}">
+ <include name="lib/jbpm*.jar" />
+ <include name="lib/jboss-el.jar" />
+ <include name="lib/drools-*.jar"/>
+ <include name="lib/core.jar"/>
+ <include name="lib/janino*.jar"/>
+ <include name="lib/antlr-*.jar"/>
+ <include name="lib/mvel*.jar"/>
+ <include name="lib/richfaces-api*.jar" />
+
+ <!-- Hibernate and deps -->
+ <include name="lib/hibernate.jar"/>
+ <include name="lib/hibernate-commons-annotations.jar"/>
+ <include name="lib/hibernate-annotations.jar"/>
+ <include name="lib/hibernate-entitymanager.jar"/>
+ <include name="lib/hibernate-validator.jar"/>
+ <include name="lib/jboss-common-core.jar" />
+
+ <!-- jsf libs -->
+ <include name="lib/jsf-api.jar" />
+ <include name="lib/jsf-impl.jar" />
+ <include name="lib/el-api.jar" />
+ <include name="lib/el-ri.jar"/>
+
+ <!-- 3rd party and supporting jars -->
+ <!--<include name="lib/log4j.jar" />-->
+ <include name="lib/javassist.jar"/>
+ <include name="lib/dom4j.jar" />
+ <include name="lib/jboss-archive-browsing.jar" />
+ <include name="lib/concurrent.jar" />
+ <include name="lib/cglib.jar"/>
+ <include name="lib/asm.jar"/>
+ <include name="lib/antlr.jar" />
+ <include name="lib/commons-logging.jar" />
+ <include name="lib/commons-collections.jar" />
+
+ <!-- seam jar -->
+ <include name="lib/jboss-seam.jar" />
+
+</fileset>]]></programlisting>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ <section>
+ <title> Building and deploying the seam-gen'd application to Websphere
+ </title>
+
+
+ <itemizedlist>
+ <listitem>
+ <para> Build your application by calling
+ <literal>ant</literal> in the base directory of your
+ project (ex.
+ <literal>/home/jbalunas/workspace/websphere_example</literal>
+ ). The target of the build will be
+ <literal>dist/websphere_example.ear</literal> . </para>
+ </listitem>
+
+ <listitem>
+ <para>To deploy the application follow the instructions here :
+ <xref linkend="jee5-websphere-deploy"/> but use references to
+ this project <literal>websphere_example</literal> instead of
+ <literal>jboss-seam-jee5</literal>.</para>
+ </listitem>
+ <listitem>
+ <para> Checkout the app at:
+ <literal>http://localhost:9080/websphere_example/index.html</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ </section>
+
</chapter>
16 years, 11 months
- 1
- 0
Seam SVN: r7288 - branches/Seam_2_0/doc/reference/en/modules.
by seam-commits＠lists.jboss.org
Author: jbalunas(a)redhat.com
Date: 2008-01-29 11:17:05 -0500 (Tue, 29 Jan 2008)
New Revision: 7288
Modified:
branches/Seam_2_0/doc/reference/en/modules/websphere.xml
Log:
added seam-gen section to chapter
Modified: branches/Seam_2_0/doc/reference/en/modules/websphere.xml
===================================================================
--- branches/Seam_2_0/doc/reference/en/modules/websphere.xml 2008-01-29 15:35:53 UTC (rev 7287)
+++ branches/Seam_2_0/doc/reference/en/modules/websphere.xml 2008-01-29 16:17:05 UTC (rev 7288)
@@ -51,6 +51,13 @@
profile with the EJB3 feature pack enabled, or augment one of your
existing ones. This can also be done after the installation
by running the profile managment tool.</para>
+ <note>
+ <title>A note about restarting the server</title>
+ <para>There are times that restarting the server will be required after
+ deploying or changes the examples in this chapter. Its does not seem
+ like every change requires a restart. If you get errors or exceptions
+ after modifing a property or deploying an application try to restart
+ the server. </para> </note>
</section>
<section>
@@ -940,4 +947,564 @@
</section>
+ <section>
+ <title>Deploying an application created using
+ <literal>seam-gen</literal> on Websphere 6.1.0.13</title>
+
+ <para><literal>seam-gen</literal> is a very useful tool for developers
+ to quickly get an application up and running, and provides a foundation
+ to add your own functionality. Out of box <literal>seam-gen</literal>
+ will produce applications configured to run on JBoss AS. These
+ instructions will show the steps needed to get it to run on Websphere.
+ As stated above in <xref linkend="jee5-websphere-section"/> there
+ are some tricky changes needed to get an EJB3 application running. This
+ section will take you through the exact steps.</para>
+
+ <para>The first step is setting up <literal>seam-gen</literal> to
+ construct the base project. There are several choices made below,
+ specifically the datasource and hibernate values that we will adjust
+ once the project is created.</para>
+
+
+ <programlisting><![CDATA[
+./seam setup
+Buildfile: build.xml
+
+init:
+
+setup:
+ [echo] Welcome to seam-gen :-)
+ [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]
+/home/jbalunas/workspace
+ [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]
+/home/jbalunas/jboss/jboss-4.2.2.GA
+ [input] Enter the project name [myproject] [myproject]
+websphere_example
+ [echo] Accepted project name as: websphere_example
+ [input] Do you want to use ICEFaces instead of RichFaces [n] (y, [n], )
+
+ [input] skipping input as property icefaces.home.new has already been set.
+ [input] Select a RichFaces skin [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)
+
+ [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )
+
+ [input] Enter the Java package name for your session beans [com.mydomain.websphere_example] [com.mydomain.websphere_example]
+org.jboss.seam.tutorial.websphere.action
+ [input] Enter the Java package name for your entity beans [org.jboss.seam.tutorial.websphere.action] [org.jboss.seam.tutorial.websphere.action]
+org.jboss.seam.tutorial.websphere.model
+ [input] Enter the Java package name for your test cases [org.jboss.seam.tutorial.websphere.action.test] [org.jboss.seam.tutorial.websphere.action.test]
+org.jboss.seam.tutorial.websphere.test
+ [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)
+
+ [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]
+
+ [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]
+
+ [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] [org.hsqldb.jdbcDriver]
+
+ [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.]
+
+ [input] Enter database username [sa] [sa]
+
+ [input] Enter database password [] []
+
+ [input] Enter the database schema name (it is OK to leave this blank) [] []
+
+ [input] Enter the database catalog name (it is OK to leave this blank) [] []
+
+ [input] Are you working with tables that already exist in the database? [n] (y, [n], )
+
+ [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )
+
+[propertyfile] Creating new property file: /rhdev/projects/jboss-seam/svn-seam_2_0/jboss-seam-2_0/seam-gen/build.properties
+ [echo] Installing JDBC driver jar to JBoss server
+ [copy] Copying 1 file to /home/jbalunas/jboss/jboss-4.2.2.GA/server/default/lib
+ [echo] Type 'seam create-project' to create the new project
+
+BUILD SUCCESSFUL
+Total time: 3 minutes 5 seconds]]></programlisting>
+
+ <para> Type <literal>./seam new-project</literal> to create your
+ project and <literal>cd
+ /home/jbalunas/workspace/websphere_example</literal> to the
+ newly created structure. </para>
+
+ </section>
+ <section>
+ <title>Changes needed for deployment to Websphere</title>
+ <para>We now need to make some changes to the generated project.</para>
+ <section>
+ <title>Configuration file changes</title>
+ <variablelist>
+ <varlistentry>
+ <term>
+ <literal>resources/META-INF/persistence-dev.xml</literal>
+ </term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Alter the
+ <literal>jta-data-source</literal> to be
+ <literal>DefaultDatasource</literal>. We are
+ going to be using the integrated Websphere
+ DB.</para>
+ </listitem>
+ <listitem>
+ <para> Add or change the properties below.
+ These are described in detail at <xref
+ linkend="jee5-websphere-section"/>:
+ </para>
+
+ <programlisting><![CDATA[
+<property name="hibernate.dialect" value="GlassfishDerbyDialect"/>
+<property name="hibernate.hbm2ddl.auto" value="update"/>
+<property name="hibernate.show_sql" value="true"/>
+<property name="hibernate.format_sql" value="true"/>
+<property name="hibernate.cache.provider_class"
+ value="org.hibernate.cache.HashtableCacheProvider"/>
+<property name="hibernate.transaction.manager_lookup_class"
+ value="org.hibernate.transaction.WebSphereExtendedJTATransactionLookup"/>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> Remove the JBoss AS specific method of exposing
+ the EntityManagerFactory: </para>
+
+ <programlisting><![CDATA[<property
+ name="jboss.entity.manager.factory.jndi.name"
+ value="java:/websphere_exampleEntityManagerFactory">]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> You'll need to alter
+ <literal>persistence-prod.xml</literal> as
+ well if you want to deploy to Websphere using the
+ prod profile. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/GlassfishDerbyDialect.class</literal>
+ </term>
+ <listitem>
+ <para>As with other examples we need to include this class for
+ DB support. It can be copied from the
+ <literal>jpa</literal> example into the
+ <literal>websphere_example/resources</literal>
+ directory.
+
+ <programlisting><![CDATA[
+cp $SEAM/examples/jpa/resources-websphere61/WEB-INF/classes/GlassfishDerbyDialect.class
+ ./resources]]></programlisting>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/META-INF/jboss-app.xml</literal>
+ </term>
+ <listitem>
+ <para> You can delete this file as we aren't deploying to JBoss
+ AS ( <literal>jboss-app.xml</literal> is used to enable
+ classloading isolation in JBoss AS) </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term> <literal>resources/*-ds.xml</literal>
+ </term>
+ <listitem>
+ <para> You can delete these file as we aren't deploying to
+ JBoss AS (these files define datasources in JBoss AS, we
+ are using Websphere's default datasource) </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
+ <literal>resources/WEB-INF/components.xml</literal>
+ </term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Enable container managed transaction
+ integration - add the <literal>
+ <transaction:ejb-transaction />
+ </literal> component, and it's namespace
+ declaration <literal>
+ xmlns:transaction="http://jboss.com/products/seam/transaction"
+ </literal> </para>
+ </listitem>
+ <listitem>
+ <para> Alter the <literal>jndi-pattern</literal>
+ to <literal>
+ java:comp/env/websphere_example/#{ejbName}
+ </literal> </para>
+ </listitem>
+ <listitem>
+ <para>We do not need
+ <literal>managed-persistence-context</literal>
+ for this example and so can delete its
+ entry.</para>
+
+
+ <programlisting><![CDATA[
+<persistence:managed-persistence-context name="entityManager"
+ auto-create="true"
+ persistence-unit-jndi-name="java:/websphere_exampleEntityManagerFactory"/> ]]></programlisting>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term> <literal>resources/WEB-INF/web.xml</literal>
+ </term>
+ <listitem>
+ <para> Websphere does not support <literal>Servlet
+ 2.5</literal>, it required <literal>Servlet
+ 2.4</literal>. For this change we need to adjust the top of
+ the <literal>web.xml</literal> file to look like the
+ following:</para>
+
+ <programlisting><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<web-app version="2.4"
+ xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
+ ]]></programlisting>
+
+ <para>As with the <literal>jee5/booking</literal>
+ example we need to add EJB references to the web.xml. These
+ references require the empty
+ <literal>local-home</literal> to flag them for
+ Websphere to perform the proper binding.</para>
+
+
+ <programlisting><![CDATA[
+ <ejb-local-ref>
+ <ejb-ref-name>websphere_example/AuthenticatorAction</ejb-ref-name>
+ <ejb-ref-type>Session</ejb-ref-type>
+ <local-home></local-home>
+ <local>org.jboss.seam.tutorial.websphere.action.Authenticator</local>
+ </ejb-local-ref>
+
+ <ejb-local-ref>
+ <ejb-ref-name>websphere_example/EjbSynchronizations</ejb-ref-name>
+ <ejb-ref-type>Session</ejb-ref-type>
+ <local-home></local-home>
+ <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>
+ </ejb-local-ref>]]></programlisting>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section>
+ <title>Creating the <literal>AuthenticatorAction</literal>
+ EJB</title>
+ <para> We want to take the existing <literal>Authenticator</literal>
+ Seam POJO component and create an EJB3 out of it. </para>
+ <orderedlist>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para> Rename the class to
+ <literal>AuthenticatorAction</literal> </para>
+ </listitem>
+ <listitem>
+ <para> Add the <literal>@Stateless</literal>
+ annotation to the new
+ <literal>AuthenticatorAction</literal> class.
+ </para>
+ </listitem>
+ <listitem>
+ <para> Create an interface called
+ <literal>Authenticator</literal> which
+ <literal>AuthenticatorAction</literal>
+ implements (EJB3 requires session beans to have a
+ local interface). Annotate the interface with
+ <literal>@Local</literal> , and add a single method
+ with same signature as the
+ <literal>authenticate</literal> in
+ <literal>AuthenticatorAction</literal> . </para>
+ </listitem>
+ </itemizedlist>
+
+
+ <programlisting><![CDATA[
+@Name("authenticator") @Stateless public class
+ AuthenticatorAction implements Authenticator {]]></programlisting>
+
+
+ <programlisting><![CDATA[
+@Local public interface Authenticator {
+ public boolean authenticate();
+}]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>We've already added its reference to the
+ <literal>web.xml</literal> file so are good to go. </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section>
+ <title>Extra jar dependencies and other changes to the
+ <literal>build.xml</literal></title>
+ <para> This application has similar requirements as the
+ <literal>jee5/booking</literal> example. </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Change the default target to
+ <literal>archive</literal> (we aren't going to cover
+ automatic deployment to Websphere).
+
+
+ <programlisting><![CDATA[
+<project name="websphere_example" default="archive" basedir=".">]]></programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Websphere looks for the drools
+ <literal>/security.drl</literal> file in the root of the
+ <literal>war</literal> file instead of the root of the
+ <literal>websphere_example.jar</literal> so we need
+ to have the <literal>build.xml</literal> move it to the
+ correct location at build time. The following must be added at
+ the top of the <literal> <target name="war"
+ depends="compile" description="Build the distribution
+ .war file"> </literal> target.
+
+ <programlisting><![CDATA[
+<copy todir="${war.dir}">
+ <fileset dir="${basedir}/resources" >
+ <include name="*.drl" />
+ </fileset>
+</copy>]]></programlisting></para>
+ </listitem>
+ <listitem>
+ <para>We need to ge the
+ <literal>GlassfishDerbyDialect.class</literal> into
+ our application jar. To do that find the
+ <literal>jar</literal> task and modify the top of it so that
+ it looks like this:
+
+
+ <programlisting><![CDATA[
+<target name="jar" depends="compile,copyclasses"
+ description="Build the distribution .jar file">
+ <copy todir="${jar.dir}">
+ <fileset dir="${basedir}/resources">
+ <include name="seam.properties" />
+ <include name="*.drl" />
+ <include name="GlassfishDerbyDialect.class" />
+ </fileset>
+ </copy>
+...]]></programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Next we need to get the
+ <literal>jboss-seam.jar</literal> into the base of the
+ <literal>EAR</literal> file. For deployment Websphere
+ requires this jar to be in both the <literal>/lib</literal>
+ directory and at the base of the <literal>EAR</literal>. You
+ must add the following to the <literal>archive</literal>
+ task: </para>
+
+
+ <programlisting><![CDATA[
+<fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+</fileset>]]></programlisting>
+ <para>So that the whole <literal>archive</literal> task looks
+ like:</para>
+
+
+ <programlisting><![CDATA[
+<target name="archive" depends="jar,war,ear"
+ description="Package the archives">
+ <jar jarfile="${dist.dir}/${project.name}.jar" basedir="${jar.dir}"/>
+ <jar jarfile="${dist.dir}/${project.name}.war" basedir="${war.dir}"/>
+ <jar jarfile="${dist.dir}/${project.name}.ear">
+ <fileset dir="${ear.dir}"/>
+ <fileset dir="${dist.dir}">
+ <include name="${project.name}.jar"/>
+ <include name="${project.name}.war"/>
+ </fileset>
+ <fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+ </fileset>
+ </jar>
+</target>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>Now we need to get extra jars into the
+ <literal>build.xml</literal>. Look for the
+ <literal><fileset dir="${basedir}"></literal> section
+ of the task below. Add the new includes at the bottom of
+ the fileset.
+ </para>
+
+
+ <programlisting><![CDATA[
+<target name="ear" description="Build the EAR">
+ <copy todir="${ear.dir}">
+ <fileset dir="${basedir}/resources">
+ <include name="*jpdl.xml" />
+ <include name="*hibernate.cfg.xml" />
+ <include name="jbpm.cfg.xml" />
+ </fileset>
+ <fileset dir="${lib.dir}">
+ <include name="jboss-seam.jar" />
+ </fileset>
+ <fileset dir="${basedir}">
+ <include name="lib/jbpm*.jar" />
+ <include name="lib/jboss-el.jar" />
+ <include name="lib/drools-*.jar"/>
+ <include name="lib/core.jar"/>
+ <include name="lib/janino*.jar"/>
+ <include name="lib/antlr-*.jar"/>
+ <include name="lib/mvel*.jar"/>
+ <include name="lib/richfaces-api*.jar" />
+ </fileset>
+ </copy>
+ <copy todir="${ear.dir}/META-INF">
+ <fileset dir="${basedir}/resources/META-INF">
+ <include name="application.xml" />
+ <include name="jboss-app.xml" />
+ </fileset>
+ </copy>
+</target>]]></programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>Hibernate dependencies</para>
+ <programlisting><![CDATA[
+ <!-- Hibernate and deps -->
+ <include name="lib/hibernate.jar"/>
+ <include name="lib/hibernate-commons-annotations.jar"/>
+ <include name="lib/hibernate-annotations.jar"/>
+ <include name="lib/hibernate-entitymanager.jar"/>
+ <include name="lib/hibernate-validator.jar"/>
+ <include name="lib/jboss-common-core.jar" />]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>JSF dependencies. You will need to copy the
+ <literal>el-ri.jar</literal> from the
+ <literal>$SEAM/examples/jpa/lib</literal> directory.</para>
+ <programlisting><![CDATA[
+ <!-- jsf libs -->
+ <include name="lib/jsf-api.jar" />
+ <include name="lib/jsf-impl.jar" />
+ <include name="lib/el-api.jar" />
+ <include name="lib/el-ri.jar"/>]]></programlisting>
+ </listitem>
+ <listitem>
+ <para> Third party dependencies. You will need to copy the
+ <literal>jboss-archive-browsing.jar</literal> from the
+ <literal>$SEAM/examples/jpa/lib</literal> directory into the
+ the projects <literal>/lib</literal> directory. You will
+ also need to acquire the <literal>concurrent.jar</literal>
+ and place it in the same directory. You can get this from
+ any jboss distribution or just search for it.</para>
+ <programlisting><![CDATA[
+ <!-- 3rd party and supporting jars -->
+ <!--<include name="lib/log4j.jar" />-->
+ <include name="lib/javassist.jar"/>
+ <include name="lib/dom4j.jar" />
+ <include name="lib/jboss-archive-browsing.jar" />
+ <include name="lib/concurrent.jar" />
+ <include name="lib/cglib.jar"/>
+ <include name="lib/asm.jar"/>
+ <include name="lib/antlr.jar" />
+ <include name="lib/commons-logging.jar" />
+ <include name="lib/commons-collections.jar" />]]></programlisting>
+ </listitem>
+ <listitem>
+ <para><literal>jboss-seam.jar</literal> - this is needed in
+ both the <literal>ear</literal> base and
+ <literal>/lib</literal>
+ directory.</para>
+ <programlisting><![CDATA[
+ <!-- seam jar -->
+ <include name="lib/jboss-seam.jar" />]]></programlisting>
+ </listitem>
+ </itemizedlist>
+
+ <para>You should end up with something like:</para>
+ <programlisting><![CDATA[
+<fileset dir="${basedir}">
+ <include name="lib/jbpm*.jar" />
+ <include name="lib/jboss-el.jar" />
+ <include name="lib/drools-*.jar"/>
+ <include name="lib/core.jar"/>
+ <include name="lib/janino*.jar"/>
+ <include name="lib/antlr-*.jar"/>
+ <include name="lib/mvel*.jar"/>
+ <include name="lib/richfaces-api*.jar" />
+
+ <!-- Hibernate and deps -->
+ <include name="lib/hibernate.jar"/>
+ <include name="lib/hibernate-commons-annotations.jar"/>
+ <include name="lib/hibernate-annotations.jar"/>
+ <include name="lib/hibernate-entitymanager.jar"/>
+ <include name="lib/hibernate-validator.jar"/>
+ <include name="lib/jboss-common-core.jar" />
+
+ <!-- jsf libs -->
+ <include name="lib/jsf-api.jar" />
+ <include name="lib/jsf-impl.jar" />
+ <include name="lib/el-api.jar" />
+ <include name="lib/el-ri.jar"/>
+
+ <!-- 3rd party and supporting jars -->
+ <!--<include name="lib/log4j.jar" />-->
+ <include name="lib/javassist.jar"/>
+ <include name="lib/dom4j.jar" />
+ <include name="lib/jboss-archive-browsing.jar" />
+ <include name="lib/concurrent.jar" />
+ <include name="lib/cglib.jar"/>
+ <include name="lib/asm.jar"/>
+ <include name="lib/antlr.jar" />
+ <include name="lib/commons-logging.jar" />
+ <include name="lib/commons-collections.jar" />
+
+ <!-- seam jar -->
+ <include name="lib/jboss-seam.jar" />
+
+</fileset>]]></programlisting>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ <section>
+ <title> Building and deploying the seam-gen'd application to Websphere
+ </title>
+
+
+ <itemizedlist>
+ <listitem>
+ <para> Build your application by calling
+ <literal>ant</literal> in the base directory of your
+ project (ex.
+ <literal>/home/jbalunas/workspace/websphere_example</literal>
+ ). The target of the build will be
+ <literal>dist/websphere_example.ear</literal> . </para>
+ </listitem>
+
+ <listitem>
+ <para>To deploy the application follow the instructions here :
+ <xref linkend="jee5-websphere-deploy"/> but use references to
+ this project <literal>websphere_example</literal> instead of
+ <literal>jboss-seam-jee5</literal>.</para>
+ </listitem>
+ <listitem>
+ <para> Checkout the app at:
+ <literal>http://localhost:9080/websphere_example/index.html</literal>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+ </section>
+
</chapter>
16 years, 11 months
- 1
- 0
Seam SVN: r7287 - branches/Seam_2_0/doc/reference/en/modules.
by seam-commits＠lists.jboss.org
Author: pete.muir(a)jboss.org
Date: 2008-01-29 10:35:53 -0500 (Tue, 29 Jan 2008)
New Revision: 7287
Modified:
branches/Seam_2_0/doc/reference/en/modules/websphere.xml
Log:
Some minor corrections (backport)
Modified: branches/Seam_2_0/doc/reference/en/modules/websphere.xml
===================================================================
--- branches/Seam_2_0/doc/reference/en/modules/websphere.xml 2008-01-29 15:26:43 UTC (rev 7286)
+++ branches/Seam_2_0/doc/reference/en/modules/websphere.xml 2008-01-29 15:35:53 UTC (rev 7287)
@@ -57,7 +57,7 @@
<title>Required custom properties</title>
<para>There are a couple of Websphere custom properties that are required
for Seam integration. These properties are not needed specifically
- 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 : <ulink
url="http://www-1.ibm.com/support/docview.wss?rss=180&uid=swg21284395">
Setting web container custom properties</ulink></para>
@@ -147,7 +147,7 @@
change because this is not full <literal>jee5</literal>
implementation. </para>
<para> Websphere does not support <literal>Servlet
- 2.5</literal>, it required <literal>Servlet
+ 2.5</literal>, it requires <literal>Servlet
2.4</literal>. For this change we need to adjust the top of
the <literal>web.xml</literal> file to look like the
following:</para>
@@ -161,7 +161,7 @@
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
]]></programlisting>
- <para>Next you have to make some changes to the EJB references
+ <para>Next we have to make some changes to the EJB references
in the <literal>web.xml</literal>. 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 @@
<local-home></local-home>
<local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>
</ejb-local-ref>]]></programlisting>
- <para>The important changes are that there is an empty
+ <para>The important change is that there is an empty
<literal>local-home</literal> element for each EJB.
- This is the signal to Websphere so that it will make the
- correct bindings behind the scenes between the web module
- and the EJB3 beans. The <literal>ejb-link</literal>
- element is simply not used. </para>
+ This tells Websphere to make the correct bindings between
+ the web module and the EJB3 beans. The
+ <literal>ejb-link</literal> element is simply not used.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
@@ -235,13 +235,13 @@
<listitem>
<para>For this example we will be using the default
datasource that comes with Websphere. To do this change the
- <literal>jta-data-source</literal> element like below.</para>
+ <literal>jta-data-source</literal> element:</para>
<programlisting><![CDATA[
<jta-data-source>DefaultDatasource</jta-data-source>
]]></programlisting>
<para>Then we need to adjust some of the hibernate
properties. First comment out the Glassfish properties.
- Next you need to add/change the properties below. </para>
+ Next you need to add/change the properties:</para>
<programlisting><![CDATA[
@@ -257,7 +257,7 @@
<listitem>
<para>
<literal>hibernate.transaction.manager_lookup_class</literal>
- — Standard hibernate transaction
+ — Standard Hibernate transaction
manager property for Websphere 6.X</para>
</listitem>
<listitem>
@@ -270,10 +270,8 @@
EJBContext is looked up.
- <programlisting><![CDATA[
-com.ibm.wsspi.injectionengine.InjectionException:
- EJBContext may only be looked up by or injected into an EJB
- ]]></programlisting></para>
+ <programlisting><![CDATA[com.ibm.wsspi.injectionengine.InjectionException:
+ EJBContext may only be looked up by or injected into an EJB]]></programlisting></para>
</listitem>
<listitem>
<para><literal>hibernate.dialect</literal>
@@ -357,7 +355,7 @@
<listitem>
<para>Since Websphere is not a fully compliant
<literal>JEE5</literal> implementation we need to
- add these expression language libraries as well:
+ add these EL libraries:
<itemizedlist>
<listitem>
<para><literal>el-api.jar</literal>
@@ -378,12 +376,11 @@
the <literal>/lib</literal> of the EAR.</para>
</listitem>
<listitem>
- <para>Then finally by removing the
- <literal>log4j.jar</literal> 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.</para>
+ <para>Finally we remove the <literal>log4j.jar</literal>
+ so that all of the log output from our application will
+ be added to the Websphere log. Additional steps are
+ required to fully configure log4j and those are outside
+ of the scope of this document.</para>
</listitem>
</itemizedlist> </para>
@@ -397,7 +394,7 @@
default fileset that is used to populate the
<literal>jboss-seam-jee5.jar</literal>. The primary change
is the addition of the
- <literal>GlassfishDerbyDialect.class</literal>.
+ <literal>GlassfishDerbyDialect.class</literal>:
<programlisting><![CDATA[
@@ -412,7 +409,7 @@
<para>Next we need to add the library dependencies discussed above.
For this add the following to bottom of the
- <literal>ear.lib.extras</literal> fileset entry.
+ <literal>ear.lib.extras</literal> fileset entry:
<programlisting><![CDATA[
@@ -426,7 +423,7 @@
</para>
<para>Now all that is left is to execute the <literal>ant
- archive</literal> task and your application files should be in
+ archive</literal> task and the built application will be in
the <literal>jee5/booking/dist</literal> directory.
</para>
</section>
@@ -437,8 +434,8 @@
<title>Deploying the application to Websphere</title>
<para>So now we have everything we need in place. All that is left is to
- deploy it - just a few steps more ;) </para>
- <para> For that we will use Websphere's administration console. As
+ deploy it - just a few steps more.</para>
+ <para> For this we will use Websphere's administration console. As
before there are some tricks and tips that must be followed.</para>
<para>The steps below are for the Websphere version stated above, yours
@@ -461,7 +458,7 @@
<para>At the top of the <literal>Enterprise
Application</literal> table select
<literal>Install</literal>. Below are installation
- wizard pages and what needs to done on each.
+ wizard pages and what needs to done on each:
<itemizedlist>
<listitem>
<para><literal>Preparing for the application
@@ -574,7 +571,7 @@
</listitem>
<listitem id="websphere-app-adj-after-install" xreflabel="installation adjustments for jee5 example">
<para>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:
<itemizedlist>
<listitem>
<para>Starting from the <literal>Enterprise
@@ -593,7 +590,7 @@
</listitem>
<listitem>
<para>Change the <literal>Class loader
- order</literal> combo box to say
+ order</literal> combo box to
<literal>Classes loaded with application
class loader first</literal>.</para>
</listitem>
@@ -628,11 +625,11 @@
</listitem>
<listitem>
<para>You should verify that the change you just
- made has stuck. We had problems with the last
+ made has been remembered. We have had problems 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:
<itemizedlist>
<listitem>
<para> Open the following file in a text
16 years, 11 months
- 1
- 0
Seam SVN: r7286 - trunk/doc/reference/en/modules.
by seam-commits＠lists.jboss.org
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
===================================================================
--- trunk/doc/reference/en/modules/websphere.xml 2008-01-29 15:22:12 UTC (rev 7285)
+++ trunk/doc/reference/en/modules/websphere.xml 2008-01-29 15:26:43 UTC (rev 7286)
@@ -57,7 +57,7 @@
<title>Required custom properties</title>
<para>There are a couple of Websphere custom properties that are required
for Seam integration. These properties are not needed specifically
- 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 : <ulink
url="http://www-1.ibm.com/support/docview.wss?rss=180&uid=swg21284395">
Setting web container custom properties</ulink></para>
@@ -147,7 +147,7 @@
change because this is not full <literal>jee5</literal>
implementation. </para>
<para> Websphere does not support <literal>Servlet
- 2.5</literal>, it required <literal>Servlet
+ 2.5</literal>, it requires <literal>Servlet
2.4</literal>. For this change we need to adjust the top of
the <literal>web.xml</literal> file to look like the
following:</para>
@@ -161,7 +161,7 @@
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
]]></programlisting>
- <para>Next you have to make some changes to the EJB references
+ <para>Next, er have to make some changes to the EJB references
in the <literal>web.xml</literal>. 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 @@
<local-home></local-home>
<local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>
</ejb-local-ref>]]></programlisting>
- <para>The important changes are that there is an empty
+ <para>The important change is that there is an empty
<literal>local-home</literal> element for each EJB.
- This is the signal to Websphere so that it will make the
- correct bindings behind the scenes between the web module
- and the EJB3 beans. The <literal>ejb-link</literal>
- element is simply not used. </para>
+ This tells Websphere to make the correct bindings between
+ the web module and the EJB3 beans. The
+ <literal>ejb-link</literal> element is simply not used.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
@@ -235,13 +235,13 @@
<listitem>
<para>For this example we will be using the default
datasource that comes with Websphere. To do this change the
- <literal>jta-data-source</literal> element like below.</para>
+ <literal>jta-data-source</literal> element:</para>
<programlisting><![CDATA[
<jta-data-source>DefaultDatasource</jta-data-source>
]]></programlisting>
<para>Then we need to adjust some of the hibernate
properties. First comment out the Glassfish properties.
- Next you need to add/change the properties below. </para>
+ Next you need to add/change the properties:</para>
<programlisting><![CDATA[
@@ -257,7 +257,7 @@
<listitem>
<para>
<literal>hibernate.transaction.manager_lookup_class</literal>
- — Standard hibernate transaction
+ — Standard Hibernate transaction
manager property for Websphere 6.X</para>
</listitem>
<listitem>
@@ -270,10 +270,8 @@
EJBContext is looked up.
- <programlisting><![CDATA[
-com.ibm.wsspi.injectionengine.InjectionException:
- EJBContext may only be looked up by or injected into an EJB
- ]]></programlisting></para>
+ <programlisting><![CDATA[com.ibm.wsspi.injectionengine.InjectionException:
+ EJBContext may only be looked up by or injected into an EJB]]></programlisting></para>
</listitem>
<listitem>
<para><literal>hibernate.dialect</literal>
@@ -341,8 +339,8 @@
<itemizedlist>
<listitem>
<para>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:
<itemizedlist>
<listitem>
<para><literal>jsf-api.jar</literal>
@@ -357,7 +355,7 @@
<listitem>
<para>Since Websphere is not a fully compliant
<literal>JEE5</literal> implementation we need to
- add these expression language libraries as well:
+ add these EL libraries:
<itemizedlist>
<listitem>
<para><literal>el-api.jar</literal>
@@ -378,12 +376,11 @@
the <literal>/lib</literal> of the EAR.</para>
</listitem>
<listitem>
- <para>Then finally by removing the
- <literal>log4j.jar</literal> 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.</para>
+ <para>Finally we remove the <literal>log4j.jar</literal>
+ so that all of the log output from our application will
+ be added to the Websphere log. Additional steps are
+ required to fully configure log4j and those are outside
+ of the scope of this document.</para>
</listitem>
</itemizedlist> </para>
@@ -397,7 +394,7 @@
default fileset that is used to populate the
<literal>jboss-seam-jee5.jar</literal>. The primary change
is the addition of the
- <literal>GlassfishDerbyDialect.class</literal>.
+ <literal>GlassfishDerbyDialect.class</literal>:
<programlisting><![CDATA[
@@ -412,7 +409,7 @@
<para>Next we need to add the library dependencies discussed above.
For this add the following to bottom of the
- <literal>ear.lib.extras</literal> fileset entry.
+ <literal>ear.lib.extras</literal> fileset entry:
<programlisting><![CDATA[
@@ -426,7 +423,7 @@
</para>
<para>Now all that is left is to execute the <literal>ant
- archive</literal> task and your application files should be in
+ archive</literal> task and the built application will be in
the <literal>jee5/booking/dist</literal> directory.
</para>
</section>
@@ -437,8 +434,8 @@
<title>Deploying the application to Websphere</title>
<para>So now we have everything we need in place. All that is left is to
- deploy it - just a few steps more ;) </para>
- <para> For that we will use Websphere's administration console. As
+ deploy it - just a few steps more.</para>
+ <para> For this we will use Websphere's administration console. As
before there are some tricks and tips that must be followed.</para>
<para>The steps below are for the Websphere version stated above, yours
@@ -461,7 +458,7 @@
<para>At the top of the <literal>Enterprise
Application</literal> table select
<literal>Install</literal>. Below are installation
- wizard pages and what needs to done on each.
+ wizard pages and what needs to done on each:
<itemizedlist>
<listitem>
<para><literal>Preparing for the application
@@ -574,7 +571,7 @@
</listitem>
<listitem id="websphere-app-adj-after-install" xreflabel="installation adjustments for jee5 example">
<para>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:
<itemizedlist>
<listitem>
<para>Starting from the <literal>Enterprise
@@ -593,7 +590,7 @@
</listitem>
<listitem>
<para>Change the <literal>Class loader
- order</literal> combo box to say
+ order</literal> combo box to
<literal>Classes loaded with application
class loader first</literal>.</para>
</listitem>
@@ -628,11 +625,11 @@
</listitem>
<listitem>
<para>You should verify that the change you just
- made has stuck. We had problems with the last
+ made has been remembered. We have had problems 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:
<itemizedlist>
<listitem>
<para> Open the following file in a text
16 years, 11 months
- 1
- 0
Seam SVN: r7285 - trunk/examples/wiki/view.
by seam-commits＠lists.jboss.org
Author: christian.bauer(a)jboss.com
Date: 2008-01-29 10:22:12 -0500 (Tue, 29 Jan 2008)
New Revision: 7285
Modified:
trunk/examples/wiki/view/dirDisplay_d.xhtml
Log:
Typo
Modified: trunk/examples/wiki/view/dirDisplay_d.xhtml
===================================================================
--- trunk/examples/wiki/view/dirDisplay_d.xhtml 2008-01-29 13:14:16 UTC (rev 7284)
+++ trunk/examples/wiki/view/dirDisplay_d.xhtml 2008-01-29 15:22:12 UTC (rev 7285)
@@ -501,7 +501,7 @@
<f:convertDateTime pattern="dd. MMM yyyy, HH:mm" timeZone="#{preferences.get('Wiki').timeZone}"/>
</h:outputText>
(<s:span styleClass="undecoratedLink">
- <h:outputLink value="#{wiki:renderUserInfoURL(node.lastModifiedBy.createdBy)}">
+ <h:outputLink value="#{wiki:renderUserInfoURL(node.lastModifiedBy)}">
<h:outputText value="#{node.lastModifiedBy.username}"/>
</h:outputLink>
</s:span>)
16 years, 11 months
- 1
- 0