4:44 p.m.
Author: manaRH
Date: 2008-10-27 17:44:08 -0400 (Mon, 27 Oct 2008)
New Revision: 9454
Modified:
branches/enterprise/JBPAPP_4_3_FP01/build.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Dependencies.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Framework.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Hsearch.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/I18n.xml
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Modified: branches/enterprise/JBPAPP_4_3_FP01/build.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/build.xml 2008-10-27 20:52:43 UTC (rev 9453)
+++ branches/enterprise/JBPAPP_4_3_FP01/build.xml 2008-10-27 21:44:08 UTC (rev 9454)
@@ -498,7 +498,7 @@
<copy file="changelog.txt" todir="${dist.dir}" />
<propertyfile file="${dist.dir}/build.properties" comment="See
build/sample.build.properties for properties you might want to set">
<entry key="tomcat.home" value="/var/lib/tomcat5" />
- <entry key="jboss.home" value="/var/lib/jbossas" />
+ <entry key="jboss.home" value="/var/lib/jboss-as" />
<entry key="mavenized" value="false" />
<entry key="qualifier" value="${qualifier}" />
</propertyfile>
Modified:
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Configuration.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -933,8 +933,7 @@
</container-cache-conf>]]></programlisting>
<para> The default HTTP session timeout can be modified in
-
<literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal>
for JBoss 4.0.x, or in
-
<literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for
JBoss 4.2.x. The following
+
<literal>server/<profile>/deploy/jboss-web.deployer/conf/web.xml</literal>
for JBoss EAP 4.3. The following
entry in this file controls the default session timeout for all web
applications: </para>
<programlisting role="XML"><![CDATA[<session-config>
Modified:
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Dependencies.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Dependencies.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Dependencies.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -48,7 +48,7 @@
type is listed as <literal>war</literal>, the library should be placed
in
the <literal>/WEB-INF/lib</literal> directory of your application's
war
file. The scope of the dependency is either all, runtime or provided (by
- JBoss AS 4.2).
+ JBoss EAP 4.3).
</para>
<para>
Modified:
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Framework.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Framework.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Framework.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -78,7 +78,7 @@
A second advantage is that your classes may be EJB stateful
session beans, if you like. (They do not have to be, they
can be plain JavaBean components if you prefer.) If you are using
- JBoss AS, you'll need 4.2.2.GA or later:
+ JBoss EAP:
</para>
<programlisting role="JAVA"><![CDATA[@Stateful
Modified:
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -24,7 +24,7 @@
<section>
<title>Before you start</title>
- <para>Make sure you have JDK 5 or JDK 6, JBoss AS 4.2 and Ant 1.6, along
with recent versions of Eclipse, the
+ <para>Make sure you have JDK 5 or JDK 6, JBoss EAP 4.3 CP02 and Ant 1.6,
along with recent versions of Eclipse, the
JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly
installed before starting. Add your
JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug
mode. Finally, start a command
prompt in the directory where you unzipped the Seam
distribution.</para>
@@ -406,41 +406,4 @@
incremental hot deployment for EAR projects.</para>
</section>
- <section>
- <title>Using Seam with JBoss 4.0</title>
-
- <para> Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss
AS, we recommend using JBoss 4.2, which
- bundles the JSF 1.2 reference implementation. However, it is still possible
to use Seam 2.0 on the JBoss 4.0
- platform. There are two basic steps required to do this: install an
EJB3-enabled version of JBoss 4.0 and
- replace MyFaces with the JSF 1.2 reference implementation. Once you complete
these steps, Seam 2.0
- applications can be deployed to JBoss 4.0.</para>
-
- <section>
- <title>Install JBoss 4.0</title>
- <para>JBoss 4.0 does not ship a default configuration compatible with
Seam. To run Seam, you must install
- JBoss 4.0.5 using the JEMS 1.2 installer with the ejb3 profile selected.
Seam will not run with an
- installation that doesn't include EJB3 support. The JEMS installer
can be downloaded from <ulink
- url="http://labs.jboss.com/jemsinstaller/downloads"
- >http://labs.jboss.com/jemsinstaller/downloads</ulink>.
</para>
- </section>
-
- <section>
- <title>Install the JSF 1.2 RI</title>
-
- <para> The web configuration for JBoss 4.0 can be found in the
-
<literal>server/default/deploy/jbossweb-tomcat55.sar</literal>. You'll
need to delete
- <literal>myfaces-api.jar</literal> any
<literal>myfaces-impl.jar</literal> from the
- <literal>jsf-libs </literal>directory. Then, you'll
need to copy <literal>jsf-api.jar</literal>,
- <literal>jsf-impl.jar</literal>,
<literal>el-api.jar</literal>, and <literal>el-ri.jar</literal>
- to that directory. The JSF JARs can be found in the Seam
<literal>lib</literal> directory. The el JARs
- can be obtained from the Seam 1.2 release. </para>
-
- <para>You'll also need to edit the
<literal>conf/web.xml</literal>, replacing
- <literal>myfaces-impl.jar</literal> with
<literal>jsf-impl.jar</literal>. </para>
- </section>
-
-
-
- </section>
-
</chapter>
Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Hsearch.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -60,7 +60,7 @@
</persistence-unit>]]></programlisting>
<para>If you plan to target Hibernate Annotations or EntityManager 3.2.x
- (embedded into JBoss AS 4.2.GA), you also need to configure the
+ (embedded into JBoss EAP AS 4.3), you also need to configure the
appropriate event listeners.</para>
<programlisting role="XML"><![CDATA[<persistence-unit
name="sample">
Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/I18n.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++ branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/I18n.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -33,8 +33,8 @@
parameters in the correct encoding from client requests you have to
configure the tomcat connector. If you use Tomcat or JBoss AS, add
the <literal>URIEncoding="UTF-8"</literal> attribute to
the
- connector configuration. For JBoss AS 4.2 change
-
<literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server.xml</literal>:
+ connector configuration. For JBoss EAP AS 4.3 change
+
<literal>${JBOSS_HOME}/server/production/deploy/jboss-web.deployer/server.xml</literal>:
</para>
<programlisting role="XML"><Connector
port="8080" URIEncoding="UTF-8"/></programlisting>
Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
---
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2008-10-27
20:52:43 UTC (rev 9453)
+++
branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2008-10-27
21:44:08 UTC (rev 9454)
@@ -6,8 +6,7 @@
<section id="try-examples">
<title>Try the examples</title>
- <para> In this tutorial, we'll assume that you have downloaded JBoss AS
4.2. You should also have a copy of
- Seam downloaded and extracted to a work directory. </para>
+ <para> In this tutorial, we'll assume that you are using JBoss EAP
4.3.</para>
<para> The directory structure of each example in Seam follows this
pattern: </para>
@@ -38,9 +37,10 @@
<title>Running the examples on JBoss AS</title>
<para> First, make sure you have Ant correctly installed, with
<literal>$ANT_HOME</literal> and
- <literal>$JAVA_HOME</literal> set correctly. Next, make
sure you set the location of your JBoss AS
- 4.2 installation in the <literal>build.properties</literal>
file in the root folder of your Seam
- installation. If you haven't already done so, start JBoss AS now by
typing <literal>bin/run.sh</literal>
+ <literal>$JAVA_HOME</literal> set correctly. Next, make
sure you set the location of your EAP embedded JBoss AS
+ installation in the <literal>build.properties</literal> file
in the root folder of your Seam
+ installation, predefined location is /var/lib/jboss-as. If you
haven't already done so,
+ start JBoss AS now by typing <literal>bin/run.sh</literal>
or <literal>bin/run.bat</literal> in the root directory of
your JBoss installation. </para>
<para> Now, build and deploy the example by typing <literal>ant
deploy</literal> in the