[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Tue Jun 26 19:36:27 EDT 2007
User: gavin
Date: 07/06/26 19:36:27
Modified: doc/reference/en/modules configuration.xml groovy.xml
hsearch.xml
Log:
doc new tx management
Revision Changes Path
1.56 +29 -1 jboss-seam/doc/reference/en/modules/configuration.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: configuration.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/configuration.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -b -r1.55 -r1.56
--- configuration.xml 26 Jun 2007 20:33:41 -0000 1.55
+++ configuration.xml 26 Jun 2007 23:36:27 -0000 1.56
@@ -364,6 +364,15 @@
servers (such as GlassFish) require you to specify JNDI names for all EJB components explicitly (and
tediously). In this case, you can pick your own pattern ;-) </para>
+ <para>
+ In an EJB3 environment, we recommend the use of a special built-in component for transaction management,
+ that is fully aware of container transactions, and can correctly process transaction success events
+ registered with the <literal>Events</literal> component. If you don't add this line to your
+ <literal>components.xml</literal> file, Seam won't know when container-managed transactions end:
+ </para>
+
+ <programlisting><![CDATA[<transaction:ejb-transaction/>]]></programlisting>
+
</sect2>
<sect2>
@@ -573,7 +582,26 @@
</sect1>
<sect1>
- <title>Configuring Seam in Java SE, with the JBoss Embedded</title>
+ <title>Configuring Seam in Java SE, without JBoss Embedded</title>
+
+ <para> It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam
+ how to manage transactions, since there will be no JTA available. If you're using JPA, you can tell
+ Seam to use JPA resource-local transactions, ie. <literal>EntityTransaction</literal>, like so: </para>
+
+ <programlisting><![CDATA[<transaction:entity-transaction entity-manager="#{entityManager}"/>]]></programlisting>
+
+ <para> If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this: </para>
+
+ <programlisting><![CDATA[<transaction:hibernate-transaction session="#{session}"/>]]></programlisting>
+
+ <para> Of course, you'll also need to define a datasource.</para>
+
+ <para> A better alternative is to use JBoss Embedded to get access to the EE APIs. </para>
+
+ </sect1>
+
+ <sect1>
+ <title>Configuring Seam in Java SE, with JBoss Embedded</title>
<para> JBoss Embedded lets you run EJB3 components outside the context of the Java EE 5 application server. This
is especially, but not only, useful for testing. </para>
1.3 +1 -1 jboss-seam/doc/reference/en/modules/groovy.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: groovy.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/groovy.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- groovy.xml 6 Jun 2007 18:47:19 -0000 1.2
+++ groovy.xml 26 Jun 2007 23:36:27 -0000 1.3
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter>
+<chapter id="groovy">
<title>Groovy integration</title>
<para>One aspect of JBoss Seam is its RAD (Rapid Application Development) capability. While not synonymous with RAD,
1.2 +1 -1 jboss-seam/doc/reference/en/modules/hsearch.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: hsearch.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/hsearch.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- hsearch.xml 24 Jun 2007 17:33:00 -0000 1.1
+++ hsearch.xml 26 Jun 2007 23:36:27 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<chapter>
+<chapter id="search">
<title>Hibernate Search</title>
<section>
More information about the jboss-cvs-commits
mailing list