Nabble - seam-commits

Seam SVN: r11679 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-24T22:22:19Z

Author: laubai
Date: 2009-11-25 01:22:18 -0500 (Wed, 25 Nov 2009)
New Revision: 11679

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
Log:
Adding changes for CP07. Not PDF-buildable in Publican.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 20:44:52 UTC (rev 11678)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-25 06:22:18 UTC (rev 11679)
@@ -417,21 +417,16 @@
</listitem>
</itemizedlist>

- <para>
+ 

- <table>
+ 

+
<thead>
<row>
<entry>
@@ -1038,7 +1033,7 @@
</row>
</tbody>
</tgroup>
- </table>
+ </table>-->

</section>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11678 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT.

2009-11-24T12:44:52Z

Author: nico.ben
Date: 2009-11-24 15:44:52 -0500 (Tue, 24 Nov 2009)
New Revision: 11678

Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Jms.po
Log:
Italian translation

Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Jms.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Jms.po 2009-11-24 16:44:00 UTC (rev 11677)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Jms.po 2009-11-24 20:44:52 UTC (rev 11678)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-13 23:52+0000\n"
-"PO-Revision-Date: 2009-11-21 21:14+0100\n"
+"PO-Revision-Date: 2009-11-24 21:44+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz@...>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -53,7 +53,7 @@
#: Jms.xml:34
#, no-c-format
msgid "This chapter first covers how to leverage Seam to simplify JMS and then explains how to use the simpler asynchronous method and event facility."
-msgstr "Questo capitolo innanzitutto spiega come sfruttare Seam per semplificare JMS e quindi spiega come usare in modo semplice metodo asincrono e facility evento."
+msgstr "Questo capitolo innanzitutto spiega come sfruttare Seam per semplificare JMS e quindi spiega come usare il più semplice metodo asincrono e facility evento."

#. Tag: title
#: Jms.xml:40

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11677 - in modules/trunk: international and 2 other directories.

2009-11-24T08:44:00Z

Author: shane.bryzak@...
Date: 2009-11-24 11:44:00 -0500 (Tue, 24 Nov 2009)
New Revision: 11677

Modified:
modules/trunk/faces/src/test/java/org/jboss/seam/faces/international/FacesMessagesTest.java
modules/trunk/international/pom.xml
modules/trunk/international/src/test/java/org/jboss/seam/international/StatusMessagesTest.java
modules/trunk/version-matrix/pom.xml
Log:
fixed up poms

Modified: modules/trunk/faces/src/test/java/org/jboss/seam/faces/international/FacesMessagesTest.java
===================================================================
--- modules/trunk/faces/src/test/java/org/jboss/seam/faces/international/FacesMessagesTest.java 2009-11-24 15:02:04 UTC (rev 11676)
+++ modules/trunk/faces/src/test/java/org/jboss/seam/faces/international/FacesMessagesTest.java 2009-11-24 16:44:00 UTC (rev 11677)
@@ -28,9 +28,9 @@
import org.jboss.testharness.impl.packaging.Artifact;
import org.jboss.testharness.impl.packaging.Classes;
import org.jboss.webbeans.context.ConversationContext;
-import org.jboss.webbeans.context.api.helpers.ConcurrentHashMapBeanStore;
import org.jboss.webbeans.log.LoggerProducer;
import org.jboss.webbeans.test.AbstractWebBeansTest;
+import org.jboss.weld.context.api.helpers.ConcurrentHashMapBeanStore;
import org.testng.annotations.Test;

/**

Modified: modules/trunk/international/pom.xml
===================================================================
--- modules/trunk/international/pom.xml 2009-11-24 15:02:04 UTC (rev 11676)
+++ modules/trunk/international/pom.xml 2009-11-24 16:44:00 UTC (rev 11677)
@@ -60,16 +60,11 @@
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>jsr299-api</artifactId>
+ <groupId>javax.enterprise</groupId>
+ <artifactId>cdi-api</artifactId>
<scope>provided</scope>
</dependency>

- <dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-logger</artifactId>
- </dependency>
-
</dependencies>

</project>

Modified: modules/trunk/international/src/test/java/org/jboss/seam/international/StatusMessagesTest.java
===================================================================
--- modules/trunk/international/src/test/java/org/jboss/seam/international/StatusMessagesTest.java 2009-11-24 15:02:04 UTC (rev 11676)
+++ modules/trunk/international/src/test/java/org/jboss/seam/international/StatusMessagesTest.java 2009-11-24 16:44:00 UTC (rev 11677)
@@ -9,9 +9,9 @@
import org.jboss.testharness.impl.packaging.Artifact;
import org.jboss.testharness.impl.packaging.Classes;
import org.jboss.webbeans.context.ConversationContext;
-import org.jboss.webbeans.context.api.helpers.ConcurrentHashMapBeanStore;
import org.jboss.webbeans.log.LoggerProducer;
import org.jboss.webbeans.test.AbstractWebBeansTest;
+import org.jboss.weld.context.api.helpers.ConcurrentHashMapBeanStore;
import org.testng.annotations.Test;

/**

Modified: modules/trunk/version-matrix/pom.xml
===================================================================
--- modules/trunk/version-matrix/pom.xml 2009-11-24 15:02:04 UTC (rev 11676)
+++ modules/trunk/version-matrix/pom.xml 2009-11-24 16:44:00 UTC (rev 11677)
@@ -54,6 +54,7 @@
<seam.version>3.0.0-SNAPSHOT</seam.version>
<seam.groupId>org.jboss.seam</seam.groupId>
<weld.version>1.0.0</weld.version>
+ <weld-ext.version>1.0.0-SNAPSHOT</weld-ext.version>
<weld.groupId>org.jboss.weld</weld.groupId>
</properties>

@@ -187,16 +188,10 @@
<dependency>
<groupId>${weld.groupId}</groupId>
<artifactId>weld-logger</artifactId>
- <version>${weld.version}</version>
+ <version>${weld-ext.version}</version>
</dependency>

<dependency>
- <groupId>${weld.groupId}</groupId>
- <artifactId>weld-logging</artifactId>
- <version>${weld.version}</version>
- </dependency>
-
- <dependency>
<groupId>${weld.groupId}.servlet</groupId>
<artifactId>weld-servlet</artifactId>
<version>${weld.version}</version>
@@ -308,6 +303,12 @@
</dependency>

<dependency>
+ <groupId>#{seam.groupId}</groupId>
+ <artifactId>seam-remoting</artifactId>
+ <version>${seam.version}</version>
+ </dependency>
+
+ <dependency>
<groupId>${seam.groupId}</groupId>
<artifactId>seam-resources</artifactId>
<version>${seam.version}</version>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11676 - in branches/enterprise/JBPAPP_4_3_FP01: examples/dvdstore/resources and 2 other directories.

2009-11-24T07:02:05Z

Author: manaRH
Date: 2009-11-24 10:02:04 -0500 (Tue, 24 Nov 2009)
New Revision: 11676

Modified:
branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml
branches/enterprise/JBPAPP_4_3_FP01/examples/dvdstore/resources/hibernate.cfg.xml
branches/enterprise/JBPAPP_4_3_FP01/examples/todo/resources/hibernate.cfg.xml
branches/enterprise/JBPAPP_4_3_FP01/src/test/integration/resources/hibernate.cfg.xml
Log:
reverting jbpm upgrade to 3.2.8

Modified: branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml 2009-11-24 12:32:01 UTC (rev 11675)
+++ branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml 2009-11-24 15:02:04 UTC (rev 11676)
@@ -254,7 +254,7 @@
<dependency>
<groupId>org.jbpm.jbpm3</groupId>
<artifactId>jbpm-jpdl</artifactId>
- <version>3.2.8</version>
+ <version>3.2.5.SP5</version>
<exclusions>
<exclusion>
<groupId>org.hibernate</groupId>

Modified: branches/enterprise/JBPAPP_4_3_FP01/examples/dvdstore/resources/hibernate.cfg.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/examples/dvdstore/resources/hibernate.cfg.xml 2009-11-24 12:32:01 UTC (rev 11675)
+++ branches/enterprise/JBPAPP_4_3_FP01/examples/dvdstore/resources/hibernate.cfg.xml 2009-11-24 15:02:04 UTC (rev 11676)
@@ -51,7 +51,6 @@


<mapping resource="org/jbpm/db/hibernate.queries.hbm.xml" />
- <mapping resource="org/jbpm/db/hibernate.types.hbm.xml"/>


<mapping resource="org/jbpm/graph/action/MailAction.hbm.xml"/>

Modified: branches/enterprise/JBPAPP_4_3_FP01/examples/todo/resources/hibernate.cfg.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/examples/todo/resources/hibernate.cfg.xml 2009-11-24 12:32:01 UTC (rev 11675)
+++ branches/enterprise/JBPAPP_4_3_FP01/examples/todo/resources/hibernate.cfg.xml 2009-11-24 15:02:04 UTC (rev 11676)
@@ -51,7 +51,6 @@


<mapping resource="org/jbpm/db/hibernate.queries.hbm.xml" />
- <mapping resource="org/jbpm/db/hibernate.types.hbm.xml"/>


<mapping resource="org/jbpm/graph/action/MailAction.hbm.xml"/>

Modified: branches/enterprise/JBPAPP_4_3_FP01/src/test/integration/resources/hibernate.cfg.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/src/test/integration/resources/hibernate.cfg.xml 2009-11-24 12:32:01 UTC (rev 11675)
+++ branches/enterprise/JBPAPP_4_3_FP01/src/test/integration/resources/hibernate.cfg.xml 2009-11-24 15:02:04 UTC (rev 11676)
@@ -40,7 +40,6 @@
######################
hql queries and type defs -->
<mapping resource="org/jbpm/db/hibernate.queries.hbm.xml"/>
- <mapping resource="org/jbpm/db/hibernate.types.hbm.xml"/>

<mapping resource="org/jbpm/graph/action/MailAction.hbm.xml"/>


_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11675 - branches/enterprise/JBPAPP_4_3_FP01/src/test/ftest/examples/blog.

2009-11-24T04:32:02Z

Author: kpiwko@...
Date: 2009-11-24 07:32:01 -0500 (Tue, 24 Nov 2009)
New Revision: 11675

Modified:
branches/enterprise/JBPAPP_4_3_FP01/src/test/ftest/examples/blog/build.xml
Log:
JBPAPP-3110

Modified: branches/enterprise/JBPAPP_4_3_FP01/src/test/ftest/examples/blog/build.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/src/test/ftest/examples/blog/build.xml 2009-11-24 08:51:59 UTC (rev 11674)
+++ branches/enterprise/JBPAPP_4_3_FP01/src/test/ftest/examples/blog/build.xml 2009-11-24 12:32:01 UTC (rev 11675)
@@ -22,6 +22,7 @@
-->
<project name="blog.ftest.build" basedir="." default="build">
<property name="example.name" value="blog" />
+ <property name="jboss.example.ready.check.url" value="seam-blog/home.seam" />

<import file="../build.xml" />
</project>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11674 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-24T00:51:59Z

Author: laubai
Date: 2009-11-24 03:51:59 -0500 (Tue, 24 Nov 2009)
New Revision: 11674

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Edited the Tutorial chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 08:09:15 UTC (rev 11673)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 08:51:59 UTC (rev 11674)
@@ -97,7 +97,7 @@
<emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra
annotations that define the class as a Seam component. </para>

- <example>
+
<formalpara><title>User.java Example</title>
<para>
<programlisting role="JAVA"><![CDATA[@Entity
@@ -198,7 +198,7 @@
</orderedlist>
</para>
</formalpara>
-</example>
+
<para> The most important things to notice in this example are the <literal>@Name</literal> and
<literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component. </para>
<para> We'll see below that the properties of our <literal>User</literal> class are bound
@@ -214,7 +214,7 @@
<section>
<title>The stateless session bean class: <literal>RegisterAction.java</literal></title>

- <para> Most Seam application use session beans as JSF action listeners (you can use JavaBeans instead if
+ <para> Most Seam applications use session beans as JSF action listeners (you can use JavaBeans instead if
you like). </para>
<para> We have exactly one JSF action in our application, and one session bean method attached to it. In
this case, we'll use a stateless session bean, since all the state associated with our action is
@@ -392,18 +392,9 @@
<section>
<title>The Seam component deployment descriptor: <literal>components.xml</literal></title>

- <para> If you've used many Java frameworks before, you'll be used to having to declare all your
- component classes in some kind of XML file that gradually grows more and more unmanageable as your
- project matures. You'll be relieved to know that Seam does not require that application components
- be accompanied by XML. Most Seam applications require a very small amount of XML that does not grow
- very much as the project gets bigger. </para>
+ <para> If you have used Java frameworks previously, you will be used to declaring your component classes in an XML file. You have probably also noticed that as a project matures, these XML files tend to become unmanageable. Fortunately, Seam does not require application components to be accompanied by XML. Most Seam applications require only a small amount of XML, which does not tend to increase in size as projects expand. </para>

- <para> Nevertheless, it is often useful to be able to provide for <emphasis>some</emphasis> external
- configuration of <emphasis>some</emphasis> components (particularly the components built in to
- Seam). You have a couple of options here, but the most flexible option is to provide this
- configuration in a file called <literal>components.xml</literal>, located in the
- <literal>WEB-INF</literal> directory. We'll use the <literal>components.xml</literal> file to tell
- Seam how to find our EJB components in JNDI: </para>
+ <para> However, it is often useful to be able to provide for some external configuration of some components, particularly the components that are built into Seam. The most flexible option, here, is to provide this configuration in a file called <filename>components.xml</filename>, located in the <filename>WEB-INF</filename> directory. The <filename>components.xml</filename> file can be used to tell Seam how to find our EJB components in JNDI: </para>
<example>
<title></title>
<programlisting role="XML">
@@ -504,17 +495,12 @@
</example>

- <para> Note that we don't need
- any JSF managed bean declarations! Our managed beans are annotated Seam components. In Seam applications,
- the <literal>faces-config.xml</literal> is used much less often than in plain JSF. </para>
+ <para> Note that JSF managed bean declarations are unnecessary because the managed beans are annotated Seam components. In Seam applications, <filename>faces-config.xml</filename> is used much less often than in plain JSF. Here, we use it simply to enable Facelets (and not JSP) as the view handler.
+ </para>

- <para> In fact, once you have all the basic descriptors set up, the <emphasis>only</emphasis> XML you
- need to write as you add new functionality to a Seam application is orchestration: navigation rules
- or jBPM process definitions. Seam takes the view that <emphasis>process flow</emphasis> and
- <emphasis>configuration data</emphasis> are the only things that truly belong in XML. </para>
+ <para> Once you have set up all the basic descriptors, the only XML you need write to add functionality to a Seam application will be for orchestration: navigation rules or jBPM process definitions. Seam operates on the principle that process flow and configuration data are all that truly belongs in XML. </para>

- <para> In this simple example, we don't even need a navigation rule, since we decided to embed the view
- id in our action code. </para>
+ <para> The previous example does not require a navigation rule, since the view ID was embedded in our action code. </para>

</section>

@@ -579,7 +565,7 @@
<title>The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</literal></title>

<para> The view pages for a Seam application could be implemented using any technology that supports
- JSF. In this example we use Facelets, because we think it's better than JSP.</para>
+ JSF. This example uses Facelets.</para>

<example>
<title></title>
@@ -638,9 +624,6 @@
</example>

- <para> This is a boring old Facelets page using some embedded EL. There is nothing specific to Seam
- here. </para>
-
</section>

<section>
@@ -681,8 +664,6 @@
<para> This deployment descriptor links modules in the enterprise archive and binds the web application
to the context root <literal>/seam-registration</literal>. </para>

- <para> We've now seen <emphasis>all</emphasis> the files in the entire application! </para>
-
</section>
</section>

@@ -813,7 +794,7 @@

<para> But <literal>MessageManagerBean</literal> is also responsible for fetching the list of messages
the first time we navigate to the message list page. There are various ways the user could navigate
- to the page, and not all of them are preceded by a JSF action—the user might have
+ to the page, and not all of them are preceded by a JSF action — the user might have
bookmarked the page, for example. So the job of fetching the message list takes place in a Seam
<emphasis>factory method</emphasis>, instead of in an action listener method. </para>

@@ -934,12 +915,11 @@
public void destroy();
}</programlisting>

- <para> From now on, we won't show local interfaces in our code examples. </para>

- <para> Let's skip over <literal>components.xml</literal>, <literal>persistence.xml</literal>,
+ <para> From this point, local interfaces are no longer shown in these code examples.
+ <literal>components.xml</literal>, <literal>persistence.xml</literal>,
<literal>web.xml</literal>, <literal>ejb-jar.xml</literal>, <literal>faces-config.xml</literal>
- and <literal>application.xml</literal> since they are much the same as the previous example, and go
- straight to the JSP. </para>
+ and <literal>application.xml</literal> operate in a similar fashion to the previous example and to directly to the JSP. </para>

</section>

@@ -1055,8 +1035,8 @@
<section>
<title>Understanding the code</title>
<para> The center of this example is the jBPM process definition. There are also two JSPs and two trivial
- JavaBeans (There was no reason to use session beans, since they do not access the database, or have any
- other transactional behavior). Let's start with the process definition: </para>
+ JavaBeans. (There was no reason to use session beans, since they do not access the database, or have any
+ other transactional behavior.) Let's start with the process definition: </para>

<formalpara><title>todo.jpdl.xml Example</title>
<para>
@@ -1531,7 +1511,7 @@
</imageobject>
</mediaobject>

- <para> Now that we have seen the pageflow, it is very, very easy to understand the rest of the application! </para>
+ <para> Now that we have seen the pageflow, it is easy to understand the rest of the application. </para>

<para> Here is the main page of the application, <literal>numberGuess.jspx</literal>: </para>

@@ -1647,7 +1627,7 @@
</example>

- <para> As is <literal>lose.jspx</literal> (which I can't be bothered copy/pasting). Finally, the JavaBean
+ <para><filename>lose.jspx</filename> is also as expected. Finally, the JavaBean
Seam component: </para>

<formalpara><title>NumberGuess.java Example</title>
@@ -1786,7 +1766,7 @@
</programlisting>

- <para> As you can see, this Seam component is pure business logic! It doesn't need to know anything at all
+ <para> As you can see, this Seam component is pure business logic. It doesn't need to know anything at all
about the user interaction flow. This makes the component potentially more reuseable. </para>

</section>
@@ -1849,50 +1829,60 @@
</mediaobject>
</screenshot>

- <para> The booking application uses JSF, EJB 3.0 and Seam, together with Facelets for the view. There is
- also a port of this application to JSF, Facelets, Seam, JavaBeans and Hibernate3. </para>
+ <para> The booking application uses JSF, EJB 3.0 and Seam, together with Facelets for the view. There is also a port of this application to JSF, Facelets, Seam, JavaBeans and Hibernate3. </para>

- <para> One of the things you'll notice if you play with this application for long enough is that it is
- extremely <emphasis>robust</emphasis>. You can play with back buttons and browser refresh and opening
- multiple windows and entering nonsensical data as much as you like and you will find it very difficult
- to make the application crash. You might think that we spent weeks testing and fixing bugs to achive
- this. Actually, this is not the case. Seam was designed to make it very straightforward to build robust
- web applications and a lot of robustness that you are probably used to having to code yourself comes
- naturally and automatically with Seam. </para>
- <para> As you browse the sourcecode of the example application, and learn how the application works, observe
- how the declarative state management and integrated validation has been used to achieve this robustness. </para>
+ <para> One of the things you will notice about this application is that it is extremely robust. You can open multiple windows, use the back and browser refresh buttons, and enter nonsensical data, but the application is difficult to crash. Seam was designed to make building robust web applications straightforward, so robustness that would previously be hand-coded comes naturally and automatically with Seam. </para>
+
+ <para> As you browse the source code of the example application and learn how the application works, pay particular attention to the way the declarative state management and integrated validation has been used to achieve this robustness. </para>

</section>

<section>
<title>Overview of the booking example</title>

- <para> The project structure is identical to the previous one, to install and deploy this application,
+ <para> The project structure is identical to the previous one. To install and deploy this application,
please refer to <xref linkend="try-examples"/>. Once you've successfully started the application, you
can access it by pointing your browser to <ulink url="http://localhost:8080/seam-booking/">
<literal>http://localhost:8080/seam-booking/</literal>
</ulink>
</para>

- <para> Just nine classes (plus six session beans local interfaces) where used to implement this application.
- Six session bean action listeners contain all the business logic for the listed features. </para>
+ <para> The application uses six session beans to implement the business logic for the following features: </para>

- <itemizedlist>
+ <itemizedlist>
<listitem>
- <para><literal>BookingListAction</literal> retrieves existing bookings for the currently logged in user. </para>
+ <para>
+ <literal>AuthenticatorAction</literal> provides the login authentication logic.
+ </para>
</listitem>
- <listitem>
- <para><literal>ChangePasswordAction</literal> updates the password of the currently logged in user.</para>
+ <listitem>
+ <para>
+ <literal>BookingListAction</literal> retrieves existing bookings for the currently logged in user.
+ </para>
</listitem>
- <listitem>
- <para><literal>HotelBookingAction</literal> implements the core functionality of the application: hotel
- room searching, selection, booking and booking confirmation. This functionality is implemented as a
- <emphasis>conversation</emphasis>, so this is the most interesting class in the application. </para></listitem>
- <listitem>
- <para><literal>RegisterAction</literal> registers a new system user.</para>
+ <listitem>
+ <para>
+ <literal>ChangePasswordAction</literal> updates the password of the currently logged in user.
+ </para>
</listitem>
+ <listitem>
+ <para>
+ <literal>HotelBookingAction</literal> implements booking and confirmation functionality. This is implemented as a <emphasis>conversation</emphasis>, so this is one of the more important classes in the application.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>HotelSearchingAction</literal> implements the hotel search functionality.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>RegisterAction</literal> registers a new system user.
+ </para>
+ </listitem>
</itemizedlist>

+
<para> Three entity beans implement the application's persistent domain model. </para>

<itemizedlist>
@@ -1909,66 +1899,36 @@

<section>
<title>Understanding Seam conversations</title>
- <para> We encourage you browse the sourcecode at your pleasure. In this tutorial we'll concentrate upon one
- particular piece of functionality: hotel search, selection, booking and confirmation. From the point of
- view of the user, everything from selecting a hotel to confirming a booking is one continuous unit of
- work, a <emphasis>conversation</emphasis>. Searching, however, is <emphasis>not</emphasis> part of the
- conversation. The user can select multiple hotels from the same search results page, in different
- browser tabs. </para>
- <para> Most web application architectures have no first class construct to represent a conversation. This
- causes enormous problems managing state associated with the conversation. Usually, Java web applications
- use a combination of two techniques: first, some state is thrown into the
- <literal>HttpSession</literal>; second, persistable state is flushed to the database after every
- request, and reconstructed from the database at the beginning of each new request. </para>
- <para> Since the database is the least scalable tier, this often results in an utterly unacceptable lack of
- scalability. Added latency is also a problem, due to the extra traffic to and from the database on every
- request. To reduce this redundant traffic, Java applications often introduce a data (second-level) cache
- that keeps commonly accessed data between requests. This cache is necessarily inefficient, because
- invalidation is based upon an LRU policy instead of being based upon when the user has finished working
- with the data. Furthermore, because the cache is shared between many concurrent transactions, we've
- introduced a whole raft of problem's associated with keeping the cached state consistent with the
- database. </para>
- <para> Now consider the state held in the <literal>HttpSession</literal>. By very careful programming, we
- might be able to control the size of the session data. This is a lot more difficult than it sounds,
- since web browsers permit ad hoc non-linear navigation. But suppose we suddenly discover a system
- requirement that says that a user is allowed to have <emphasis>mutiple concurrent
- conversations</emphasis>, halfway through the development of the system (this has happened to me).
- Developing mechanisms to isolate session state associated with different concurrent conversations, and
- incorporating failsafes to ensure that conversation state is destroyed when the user aborts one of the
- conversations by closing a browser window or tab is not for the faint hearted (I've implemented this
- stuff twice so far, once for a client application, once for Seam, but I'm famously psychotic). </para>
- <para> Now there is a better way. </para>
- <para> Seam introduces the <emphasis>conversation context</emphasis> as a first class construct. You can
- safely keep conversational state in this context, and be assured that it will have a well-defined
- lifecycle. Even better, you won't need to be continually pushing data back and forth between the
- application server and the database, since the conversation context is a natural cache of data that the
- user is currently working with. </para>
- <para> Usually, the components we keep in the conversation context are stateful session beans. (We can also
- keep entity beans and JavaBeans in the conversation context.) There is an ancient canard in the Java
- community that stateful session beans are a scalability killer. This may have been true in 1998 when
- WebFoobar 1.0 was released. It is no longer true today. Application servers like JBoss AS have extremely
- sophisticated mechanisms for stateful session bean state replication. (For example, the JBoss EJB3
- container performs fine-grained replication, replicating only those bean attribute values which actually
- changed.) Note that all the traditional technical arguments for why stateful beans are inefficient apply
- equally to the <literal>HttpSession</literal>, so the practice of shifting state from business tier
- stateful session bean components to the web session to try and improve performance is unbelievably
- misguided. It is certainly possible to write unscalable applications using stateful session beans, by
- using stateful beans incorrectly, or by using them for the wrong thing. But that doesn't mean you should
- <emphasis>never</emphasis> use them. Anyway, Seam guides you toward a safe usage model. Welcome to
- 2005. </para>
- <para> OK, I'll stop ranting now, and get back to the tutorial. </para>
+ <para>
+ This tutorial concentrates upon one particular piece of functionality: placing a hotel reservation. From the user's perspective, hotel search, selection, booking, and confirmation are one continuous unit of work — a <emphasis>conversation</emphasis>. However, from our perspective, it is important that searching remains separate so that users can select multiple hotels from the same search results page, and open distinct conversations in separate browswer tabs.
+ </para>
+ <para>
+ Most web application architectures do not have first class constructs to represent conversations, which makes managing conversational state problematic. Java web applications generally use a combination of several techniques. Some state is transferred in the URL, but what cannot be transferred here is either added to the <literal>HttpSession</literal> or recorded to the database at the beginning and end of each request.
+ </para>
+ <para>
+ Since the database is the least-scalable tier, this drastically reduces scalability. The extra traffic to and from the database also increases latency. In order to reduce redundant traffic, Java applications often introduce a data cache to store commonly-accessed data between requests. However, since invalidation is based upon an LRU policy, rather than whether the user has finished using the data, this cache is inefficient. It is also shared between concurrent transactions, which introduces further issues associated with keeping the cached state consistent with that of the database.
+ </para>
+ <para>
+ State held in the <literal>HttpSession</literal> suffers similar issues. The <literal>HttpSession</literal> is fine for storing true session data — data common to all requests between user and application — but for data related to individual request series, it does not work so well. Conversations stored here quickly break down when dealing with multiple windows or the back button. Without careful programming, data in the <literal>HttpSession</literal> can also grow quite large, which makes the session difficult to cluster. Developing mechanisms to deal with the problems these methods present (by isolating session state associated with distinct concurrent conversations, and incorporating failsafes to ensure conversation state is destroyed when a conversation is aborted) can be complicated.
+ </para>
+ <para>
+ Seam greatly improves conditions by introducing <emphasis>conversation context</emphasis> as a first class construct. Conversation state is stored safely in this context, with a well-defined lifecycle. Even better, there is no need to push data continually between the application server and the database; the conversation context is a natural cache for currently-used data.
+ </para>

- <para> The booking example application shows how stateful components with different scopes can collaborate
- together to achieve complex behaviors. The main page of the booking application allows the user to
- search for hotels. The search results are kept in the Seam session scope. When the user navigates to one
- of these hotels, a conversation begins, and a conversation scoped component calls back to the session
- scoped component to retrieve the selected hotel. </para>

- <para> The booking example also demonstrates the use of RichFaces Ajax to implement rich client behavior without
- the use of handwritten JavaScript. </para>
+ <para>
+ In the following application, the conversation context is used to store stateful session beans. These are sometimes regarded as detrimental to scalability, and in the past, they may have been. However, modern application servers have sophisticated mechanisms for stateful session bean replication. JBoss AS performs fine-grained replication, replicating only altered bean attribute values. Used correctly, stateful session beans pose no scalability problems, but for those uncomfortable or unfamiliar with the use of stateful session beans, Seam also allows the use of POJOs.
+ </para>
+ <para>
+ The booking example shows one way that stateful components with different scopes can collaborate to achieve complex behaviors. The main page of the booking application allows the user to search for hotels. Search results are stored in the Seam session scope. When the user navigate to a hotel, a conversation begins, and a conversation scoped component retrieves the selected hotel from the session scoped component.
+ </para>
+ <para>
+ The booking example also demonstrates the use of RichFaces Ajax to implement rich client behavior without handwritten JavaScript.
+ </para>
+ <para>
+ The search function is implemented with a session-scoped stateful session bean, similar to the one used in the message list example.
+ </para>

- <para> The search functionality is implemented using a session-scope stateful session bean, similar to the
- one we saw in the message list example above. </para>

<formalpara><title>HotelSearchingAction.java Example</title>
<para>
@@ -2724,7 +2684,7 @@
</programlisting>

- <para> Notice that the example is using page actions for some other functionality—the login
+ <para> Notice that the example is using page actions for some other functionality — the login
challenge, and the pageview counter. Also notice the use of a parameter in the page action method
binding. This is not a standard feature of JSF EL, but Seam lets you use it, not just for page actions,
but also in JSF method bindings. </para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11673 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-24T00:09:15Z

Author: laubai
Date: 2009-11-24 03:09:15 -0500 (Tue, 24 Nov 2009)
New Revision: 11673

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Edited part of Tutorial chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 08:00:17 UTC (rev 11672)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 08:09:15 UTC (rev 11673)
@@ -6,29 +6,27 @@
<section id="try-examples">
<title>Try the examples</title>

- <para> In this tutorial, we'll assume that you are using JBoss EAP 4.3.</para>
+ <para> Seam provides a number of example applications which demonstrate how to use a variety of Seam's features. This tutorial will guide you through a few of those examples to help you get started learning Seam. The Seam examples are located in the <filename>examples</filename> subdirectory of the Seam distribution. The first example, on registration, is in the <filename>examples/registration</filename> directory, and so on.</para>
+
+ <para>
+ Each example has the same directory structure:
+ </para>

- <para> The directory structure of each example in Seam follows this pattern: </para>
-
<itemizedlist>
<listitem>
- <para> Web pages, images and stylesheets may be found in
- <filename>examples/<replaceable>registration</replaceable>/view</filename>
+ <para> The <filename>view</filename> directory contains view-related files such as web page templates, images and stylesheets.
</para>
</listitem>
<listitem>
- <para> Resources such as deployment descriptors and data import scripts may be found in
- <filename>examples/<replaceable>registration</replaceable>/resources</filename>
+ <para> The <filename>resources</filename> directory contains deployment descriptors and other configuration files.
</para>
</listitem>
<listitem>
- <para> Java source code may be found in
- <filename>examples/<replaceable>registration</replaceable>/src</filename>
+ <para> The <filename>src</filename> directory contains the application source code.
</para>
</listitem>
<listitem>
- <para> The Ant build script is
- <filename>examples/<replaceable>registration</replaceable>/build.xml</filename>
+ <para> <filename>build.xml</filename> is the Ant script that builds and runs the example.
</para>
</listitem>
</itemizedlist>
@@ -37,10 +35,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 EAP embedded JBoss AS
+ <literal>$JAVA_HOME</literal> set correctly. Next, make sure you set the location of your Enterprise Application Platform embedded JBoss AS
installation in the <literal>build.properties</literal> file in the root folder of your Seam
installation, predefined location is /var/lib/jbossas. If you haven't already done so,
- start JBoss EAP AS now by typing <literal>bin/run.sh</literal>
+ start JBoss Enterprise Application Platform 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
@@ -99,6 +97,7 @@
<emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra
annotations that define the class as a Seam component. </para>

+ <example>
<formalpara><title>User.java Example</title>
<para>
<programlisting role="JAVA"><![CDATA[@Entity
@@ -199,7 +198,7 @@
</orderedlist>
</para>
</formalpara>
-
+</example>
<para> The most important things to notice in this example are the <literal>@Name</literal> and
<literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component. </para>
<para> We'll see below that the properties of our <literal>User</literal> class are bound

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11672 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-24T00:00:17Z

Author: laubai
Date: 2009-11-24 03:00:17 -0500 (Tue, 24 Nov 2009)
New Revision: 11672

Removed:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.ent
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.xml
Log:
Removed old book version files.

Deleted: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.ent
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.ent 2009-11-24 07:59:12 UTC (rev 11671)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.ent 2009-11-24 08:00:17 UTC (rev 11672)
@@ -1,3 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2008">
-<!ENTITY VERSION "4.3.0_CP02_FP01">

Deleted: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.xml 2009-11-24 07:59:12 UTC (rev 11671)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Seam_Reference_Guide_CP02_FP01.xml 2009-11-24 08:00:17 UTC (rev 11672)
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]>
-
-<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Tutorial.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Getting_Started_With_JBoss_Tools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Migration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Concepts.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Xml.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Events.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Conversations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Jbpm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Persistence.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Validation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Groovy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Framework.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Drools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Security.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "I18n.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Text.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Itext.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Mail.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Jms.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Cache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Webservices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Remoting.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Spring.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Hsearch.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Annotations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Components.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Controls.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Elenhancements.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Testing.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Tools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href= "Dependencies.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</book>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11671 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T23:59:12Z

Author: laubai
Date: 2009-11-24 02:59:12 -0500 (Tue, 24 Nov 2009)
New Revision: 11671

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Spring.xml
Log:
Edited Spring chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Spring.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Spring.xml 2009-11-24 07:37:05 UTC (rev 11670)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Spring.xml 2009-11-24 07:59:12 UTC (rev 11671)
@@ -11,9 +11,11 @@
<para>Spring integration in Seam is marked as technology preview, so standard support is not guaranteed.</para>
</note>

- <para>Note! The Spring integration code is included in the jboss-seam-ioc library. This dependency is required for
+ <note>
+ <para>The Spring integration code is included in the jboss-seam-ioc library. This dependency is required for
all seam-spring integration techniques covered in this chapter.</para>
-
+ </note>
+
<para>Seam's support for Spring provides the ability to: </para>

<itemizedlist>
@@ -83,18 +85,18 @@
</bean>
]]></programlisting>

- <para>Now for the caveat!</para>
+ <para>
+ However, Spring, unlike Seam, was not designed to support a stateful component model with multiple contexts. Spring injection does not occur at method invocation time, but when the Spring bean is instantiated.
+ </para>
+
+ <para>
+ The instance available when the bean is instantiated will be used for the entire life of the bean. Say you inject a Seam conversation-scoped component instance directly into a singleton Spring bean — that singleton will hold a reference to the same instance long after the conversation is over. This is called scope <emphasis>impedance</emphasis>.
+ </para>
+
+ <para>
+ Seam bijection maintains scope impedance naturally as an invocation flows through the system. In Spring, we must inject a proxy of the Seam component, and resolve the reference when the proxy is invoked.
+ </para>

- <para> Seam was designed from the ground up to support a stateful component model with multiple contexts. Spring
- was not. Unlike Seam bijection, Spring injection does not occur at method invocation time. Instead,
- injection happens only when the Spring bean is instantiated. So the instance available when the bean is
- instantiated will be the same instance that the bean uses for the entire life of the bean. For example, if a
- Seam <literal>CONVERSATION</literal>-scoped component instance is directly injected into a singleton Spring
- bean, that singleton will hold a reference to the same instance long after the conversation is over! We call
- this problem <emphasis>scope impedance</emphasis>. Seam bijection ensures that scope impedance is maintained
- naturally as an invocation flows through the system. In Spring, we need to inject a proxy of the Seam
- component, and resolve the reference when the proxy is invoked.</para>
-
<para>The <literal><seam:instance/></literal> tag lets us automatically proxy the Seam component.</para>

<programlisting role="XML"><![CDATA[<seam:instance id="seamManagedEM" name="someManagedEMComponent" proxy="true"/>
@@ -106,7 +108,7 @@
<para> This example shows one way to use a Seam-managed persistence context from a Spring bean. (For a more robust
way to use Seam-managed persistence contexts as a replacement for the Spring
<literal>OpenEntityManagerInView</literal> filter see section on
- <xref linkend="spring-persistence"/>Using a Seam Managed Persistence Context in Spring)</para>
+ <xref linkend="spring-persistence"/>.</para>
</section>

<section>
@@ -197,7 +199,7 @@
<para> The prefix of the scope name may be changed by specifying the <literal>prefix</literal> attribute in the
<literal>configure-scopes</literal> definition. (The default prefix is <literal>seam.</literal>) </para>

- <para> By default an instance of a Spring Component registered in this way is not automatically created when
+ <para> By default an instance of a Spring component registered in this way is not automatically created when
referenced using <literal>@In</literal>. To have an instance auto-created you must either specify <literal>@In(create=true)</literal>
at the injection point to identify a specific bean to be auto created or you can use the <literal>default-auto-create</literal>
attribute of <literal>configure-scopes</literal> to make all spring beans who use a seam scope auto created.</para>
@@ -228,9 +230,9 @@
transaction APIs (JPA, Hibernate, JDO, and JTA) Spring also provides tight integrations with many application
server TransactionManagers such as Websphere and Weblogic. Spring
transaction management exposes support for many advanced features such as nested
- transactions and supports full Java EE transaction propagation rules like REQUIRES_NEW and NOT_SUPPORTED. For more
+ transactions and supports full Java EE transaction propagation rules like REQUIRES_NEW and NOT_SUPPORTED. </para>

<para>To configure Seam to use Spring transactions enable the SpringTransaction component like so:</para>

@@ -251,7 +253,7 @@
an persistence context beyond the scope of a single web request
(<literal>OpenEntityManagerInViewFilter</literal>). So, it would be nice if Spring developers
could have access to a Seam managed persistence context using all of the same tools Spring provides
- for integration with JPA(e.g. <literal>PersistenceAnnotationBeanPostProcessor</literal>,
+ for integration with JPA (for example, <literal>PersistenceAnnotationBeanPostProcessor</literal>,
<literal>JpaTemplate</literal>, etc.)</para>

<para>Seam provides a way for Spring to access a Seam managed persistence context with
@@ -282,8 +284,8 @@
<property name="persistenceContextName" value="entityManager"/>
</bean>]]></programlisting>

- <para>Where 'persistenceContextName' is the name of the Seam managed persistence context component. By default
- this EntityManagerFactory has a unitName equal to the Seam component name or in this case 'entityManager'.
+ <para>Where <literal>persistenceContextName</literal> is the name of the Seam managed persistence context component. By default
+ this EntityManagerFactory has a unitName equal to the Seam component name or in this case <literal>entityManager</literal>.
If you wish to provide a different unitName you can do so by providing a persistenceUnitName like so:
</para>

@@ -330,18 +332,15 @@
<title>Using a Seam Managed Hibernate Session in Spring</title>

<para>The Seam Spring integration also provides support for complete access to a Seam managed Hibernate session
- using spring's tools. This integration is very similar to the <xref linkend="spring-persistence"/>JPA integration.</para>
+ using spring's tools. This integration is very similar to the <xref linkend="spring-persistence"/>.</para>

- <para>Like Spring's JPA integration spring's propagation model allows only one open EntityManager per
- EntityManagerFactory per transaction??? to be available to spring tools. So, the Seam Session integration works
- by wrapping a proxy SessionFactory around a Seam managed Hibernate session
- context.</para>
+ <para>Spring's propagation model allows only one open <literal>EntityManager</literal> per <literal>EntityManagerFactory</literal> to be available to Spring tools, so Seam integrates by wrapping a proxy <literal>SessionFactory</literal> around a Seam-managed Hibernate session context. </para>

<programlisting role="XML"><![CDATA[<bean id="seamSessionFactory" class="org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean">
<property name="sessionName" value="hibernateSession"/>
</bean>]]></programlisting>

- <para>Where 'sessionName' is the name of the <literal>persistence:managed-hibernate-session</literal> component.
+ <para>Where <literal>sessionName</literal> is the name of the <literal>persistence:managed-hibernate-session</literal> component.
This SessionFactory can then be used in any Spring provided tools. The integration
also provides support for calls to <literal>SessionFactory.getCurrentInstance()</literal> as long as you call
getCurrentInstance() on the <literal>SeamManagedSessionFactory</literal>.</para>
@@ -389,7 +388,7 @@
<para>Spring provides an abstraction for executing code asynchronously called a <literal>TaskExecutor</literal>.
The Spring Seam integration allows for the use of a Spring <literal>TaskExecutor</literal> for executing
immediate <literal>@Asynchronous</literal> method calls. To enable this functionality install the
- <literal>SpringTaskExecutorDispatchor</literal> and provide a spring bean defined taskExecutor like so:</para>
+ <literal>SpringTaskExecutorDispatcher</literal> and provide a spring bean defined taskExecutor like so:</para>

<programlisting role="XML"><![CDATA[<spring:task-executor-dispatcher task-executor="#{springThreadPoolTaskExecutor}"/>]]></programlisting>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11670 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T23:37:05Z

Author: laubai
Date: 2009-11-24 02:37:05 -0500 (Tue, 24 Nov 2009)
New Revision: 11670

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Testing.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Text.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Validation.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml
Log:
Edited testing, text, tools, validation, webservices and xml chapters.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Testing.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Testing.xml 2009-11-24 07:35:44 UTC (rev 11669)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Testing.xml 2009-11-24 07:37:05 UTC (rev 11670)
@@ -3,7 +3,7 @@
<para>
Most Seam applications will need at least two kinds of automated tests:
<emphasis>unit tests</emphasis>, which test a particular Seam component
- in isolation, and scripted <emphasis>integration tests</emphasis> which
+ in isolation, and <emphasis>scripted integration tests</emphasis> which
exercise all Java layers of the application (that is, everything except the
view pages).
</para>
@@ -15,7 +15,7 @@
<title>Unit testing Seam components</title>
<para>
All Seam components are POJOs. This is a great place to start if you
- want easy unit testing. And since Seam emphasises the use of bijection
+ want easy unit testing. And since Seam emphasises the use of bijection
for inter-component interactions and access to contextual objects, it's
very easy to test a Seam component outside of its normal runtime
environment.
@@ -76,11 +76,11 @@
]]></programlisting>

<para>
- You'll notice we aren't testing retrieving data from or persisting
- data to the database; nor are we testing any functionality
- provided by Seam. We are just testing the logic of our POJOs. Seam
- components don't usually depend directly upon container infrastructure,
- so most unit testing as as easy as that!
+ In this case, we aren't testing retrieving data from the database, or
+ pushing data to it; nor are we testing any functionality provided
+ by Seam. We are just testing the logic of our POJOs. Seam components
+ don't usually depend directly upon container infrastructure,
+ so most unit testing is a simple process.
</para>
<para>
However, if you want to test the entire application, read on.
@@ -93,18 +93,16 @@

<para>
Integration testing is slightly more difficult. In this case, we can't eliminate
- the container infrastructure; indeed, that is part of what is being tested! At
- the same time, we don't want to be forced to deploy our application to an
- application server to run the automated tests. We need to be able to reproduce
- just enough of the container infrastructure inside our testing environment to be
- able to exercise the whole application, without hurting performance too much.
+ the container infrastructure, as it is also being tested. At the same time, we don't
+ want to be forced to deploy our application to an application server to run the
+ automated tests. We need to be able to reproduce just enough of the container
+ infrastructure inside our testing environment to be able to exercise the whole
+ application, without hurting performance too much.
</para>

<para>
- The approach taken by Seam is to let you write tests that exercise your
- components while running inside a pruned down container environment (Seam,
- together with the JBoss Embedded container; n.b. JBoss Embedded requires
- JDK 1.5 and does not work with JDK 1.6).
+ Seam allows you to test your components while running inside a pruned down container environment. This environment, incorporating Seam and the JBoss Embedded Container, requires JDK 1.5, and does not work with
+ JDK 1.6.
</para>

<programlisting role="JAVA"><![CDATA[public class RegisterTest extends SeamTest
@@ -143,7 +141,7 @@
Occasionally, we need to be able to replace the implementation of some
Seam component that depends upon resources which are not available in
the integration test environment. For example, suppose we have some
- Seam component which is a facade to some payment processing system:
+ Seam component which is a facade to a payment processing system:
</para>

<programlisting role="JAVA"><![CDATA[@Name("paymentProcessor")
@@ -176,20 +174,19 @@
</section>

<section>
- <title>Integration testing Seam application user interactions</title>
+ <title>Integration testing Seam application User Interactions</title>

<para>
- An even harder problem is emulating user interactions. A third problem is where
- to put our assertions. Some test frameworks let us test the whole application
- by reproducing user interactions with the web browser. These frameworks have
- their place, but they are not appropriate for use at development time.
+ Emulating user interactions is a difficult, as is correctly placing our assertions.
+ Some test frameworks let us test the whole application by reproducing user
+ interactions with the web browser. These frameworks have their place, but are not
+ appropriate for use at development time.
</para>

<para>
<literal>SeamTest</literal> lets you write <emphasis>scripted</emphasis> tests,
in a simulated JSF environment. The role of a scripted test is to reproduce
- the interaction between the view and the Seam components. In other words, you
- get to pretend you are the JSF implementation!
+ the interaction between the view and the Seam components.
</para>

<para>
@@ -283,7 +280,7 @@
}]]></programlisting>

<para>
- Notice that we've extended <literal>SeamTest</literal>, which provides a
+ We have extended <literal>SeamTest</literal>, which provides a
Seam environment for our components, and written our test script as an
anonymous class that extends <literal>SeamTest.FacesRequest</literal>,
which provides an emulated JSF request lifecycle. (There is also a
@@ -296,7 +293,7 @@
<para>
You'll find plenty of integration tests for the Seam example applications
which demonstrate more complex cases. There are instructions for running
- these tests using Ant, or using the TestNG plugin for eclipse:
+ these tests using Ant, or using the TestNG plugin for Eclipse:
</para>

<mediaobject>
@@ -436,17 +433,17 @@
dependencies from <literal>lib/</literal> (e.g.
<literal>jboss-system.jar</literal>) on the classpath, these
will cause Embedded JBoss to not boot. So, just add the
- dependencies (e.g. Drools, jBPM)you need as you go.
+ dependencies (e.g. Drools, jBPM) you need as you go.
</para>

<para>
You also need to include the <literal>bootstrap/</literal>
- directory on the classpath; <literal>bootstrap/</literal> contains
+ directory on the classpath. <literal>Bootstrap/</literal> contains
the configuration for Embedded JBoss.
</para>

<para>
- And, of course you need to put your built project and tests onto
+ You also need to put your built project and tests onto
the classpath. Don't forget to put all the correct configuration
files for JPA and Seam onto the classpath as well.Seam asks
Embedded JBoss to deploy any resource (jar or directory)
@@ -458,7 +455,7 @@

<para>
By default, a generated project will use the
- <literal>java:/DefaultDS</literal> (a built in HSQL datasource in
+ <literal>java:/DefaultDS</literal> (a built-in HSQL datasource in
Embedded JBoss) for testing. If you want to use another datasource
place the <literal>foo-ds.xml</literal> into
<literal>bootstrap/deploy</literal> directory.
@@ -471,7 +468,7 @@

<para>
Seam provides TestNG support out of the box, but you can also use
- another test framework, such as JUnit, if you want.
+ another test framework, such as JUnit, if you prefer.
</para>

<para>
@@ -532,7 +529,7 @@
<para>
You need to provide a dataset for DBUnit. IMPORTANT NOTE: DBUnit supports two
formats for dataset files, flat and XML. Seam's DBUnitSeamTest assumes the flat
- format is used, so please ensure that your dataset is in this format also.
+ format is used, so please ensure that your dataset is in this format:
</para>

<programlisting role="XML"><![CDATA[<dataset>
@@ -550,7 +547,7 @@
</dataset>]]></programlisting>

<para>
- and tell Seam about it by overriding <literal>prepareDBUnitOperations()</literal>:
+ Then override the <literal>prepareDBUnitOperations()</literal> to announce the changes to Seam:
</para>

<programlisting role="JAVA"><![CDATA[protected void prepareDBUnitOperations() {
@@ -644,4 +641,4 @@

</section>

-</chapter>
\ No newline at end of file
+</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Text.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Text.xml 2009-11-24 07:35:44 UTC (rev 11669)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Text.xml 2009-11-24 07:37:05 UTC (rev 11670)
@@ -43,7 +43,7 @@
This is the second paragraph.]]></programlisting>

<para>
- (Note that a simple newline is ignored, you need an additional blank line to wrap text into a new paragraph.)
+ A simple newline will be ignored, and you need an additional blank line to wrap text into a new paragraph.
This is the HTML that results:
</para>

@@ -220,10 +220,6 @@
<tr><td>Last name:</td><td>King</td></tr>
</table>]]></programlisting>

- <para>
- But you can do much more if you want!
- </para>
-
</section>

-</chapter>
\ No newline at end of file
+</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Validation.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Validation.xml 2009-11-24 07:35:44 UTC (rev 11669)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Validation.xml 2009-11-24 07:37:05 UTC (rev 11670)
@@ -105,7 +105,7 @@
<para>
<emphasis>Note:</emphasis> specifying <literal>@NotNull</literal>
on the model does <emphasis>not</emphasis> eliminate the requirement
- for <literal>required="true"</literal> to appear on the control!
+ for <literal>required="true"</literal> to appear on the control.
This is due to a limitation of the JSF validation architecture.
</para>

@@ -144,8 +144,7 @@

<para>
This tag simply adds an <literal><s:validate></literal>
- to every input in the form. For a large form, it can save a lot
- of typing!
+ to every input in the form.
</para>

<para>
@@ -248,7 +247,7 @@
<para>
It's better style to define explicit ids for
important controls on the page, especially if you want to do
- automated testing for the UI, using some toolkit like
+ automated testing for the UI, using a toolkit like
Selenium. If you don't provide explicit ids, JSF will generate
them, but the generated values will change if you change
anything on the page.
@@ -277,10 +276,9 @@
</h:form>]]></programlisting>

<para>
- And what if you want to specify a different message to be
- displayed when validation fails? You can use the Seam message
- bundle (and all it's goodies like el expressions inside the message,
- and per-view message bundles) with the Hibernate Validator:
+ You can use the Seam message bundle (and all it's goodies like el expressions inside the message,
+ and per-view message bundles) with the Hibernate Validator to specify a different
+ message to be displayed when validation fails:
</para>

<programlisting role="JAVA"><![CDATA[public class Location {
@@ -300,4 +298,4 @@
location.zipCode.invalid = The zip code is not valid for #{location.name}
</programlisting>

-</chapter>
\ No newline at end of file
+</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml 2009-11-24 07:35:44 UTC (rev 11669)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml 2009-11-24 07:37:05 UTC (rev 11670)
@@ -45,9 +45,7 @@
<section>
<title>Conversational Web Services</title>
<para>
- So how are conversations propagated between web service requests? Seam uses a SOAP header element present
- in both the SOAP request and response messages to carry the conversation ID from the consumer to the service,
- and back again. Here's an example of a web service request that contains a conversation ID:
+ Seam uses a SOAP header element present in both the SOAP request and response messages to carry the conversation ID from the consumer to the service, and back again. Below is an example of a web service request that contains a conversation ID:
</para>

<programlisting role="XML"><![CDATA[<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
@@ -72,7 +70,7 @@
<para>
An important thing to note is that the <literal>conversationId</literal> header element must be qualified
with a namespace of <literal>http://www.jboss.org/seam/webservice</literal>, otherwise Seam will not be
- able to read the conversation ID from the request. Here's an example of a response to the above request message:
+ able to read the conversation ID from the request. Below is an example of a response to the above request message:
</para>

<programlisting role="XML"><![CDATA[<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml 2009-11-24 07:35:44 UTC (rev 11669)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml 2009-11-24 07:37:05 UTC (rev 11670)
@@ -1,12 +1,13 @@
<chapter id="xml">

- <title>Configuring Seam components</title>
+ <title>Configuring Seam Components</title>

<para>
The philosophy of minimizing XML-based configuration is extremely strong in Seam. Nevertheless,
there are various reasons why we might want to configure a Seam component using XML: to isolate
deployment-specific information from the Java code, to enable the creation of re-usable frameworks,
to configure Seam's built-in functionality, etc.
+ </para><para>
Seam provides two basic approaches to configuring components: configuration via property settings in a
properties file or in <literal>web.xml</literal>, and configuration via <literal>components.xml</literal>.
</para>
@@ -38,8 +39,8 @@
<title>Configuring components via <literal>components.xml</literal></title>

<para>
- The <literal>components.xml</literal> file is a bit more powerful than property settings. It lets
- you:
+ The <literal>components.xml</literal> file is a bit more powerful than property settings. It allows
+ you to:
</para>

<itemizedlist>
@@ -92,8 +93,11 @@
</para>

<para>
- For example, the following <literal>components.xml</literal> file installs jBPM:
+ For example, the following three examples install jBPM:
</para>
+ <para>
+ Example One:
+ </para>

<programlisting role="XML"><![CDATA[<components xmlns="http://jboss.com/products/seam/components"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -102,7 +106,7 @@
</components>]]></programlisting>

<para>
- This example does the same thing:
+ Example Two:
</para>

<programlisting role="XML"><![CDATA[<components>
@@ -125,7 +129,7 @@
</components>]]></programlisting>

<para>
- As does this one:
+ Example Three:
</para>

<programlisting role="XML"><![CDATA[<components>
@@ -203,7 +207,7 @@
</components>]]></programlisting>

<para>
- You can create an "alias" (a second name) for a Seam component like so:
+ You can create an alias for a Seam component like so:
</para>

<programlisting role="XML"><![CDATA[<components>
@@ -213,7 +217,7 @@
</components>]]></programlisting>

<para>
- You can even create an "alias" for a commonly used expression:
+ You can even create an alias for a commonly used expression:
</para>

<programlisting role="XML"><![CDATA[<components>
@@ -334,7 +338,7 @@

<para>
Finally, you may wire together components using a value-binding expression. Note that this is quite
- different to injection using <literal>@In</literal>, since it happens at component instantiation time
+ different to injection using <literal>@In</literal>, since it happens at component creation time
instead of invocation time. It is therefore much more similar to the dependency injection facilities
offered by traditional IoC containers like JSF or Spring.
</para>
@@ -396,9 +400,8 @@

<para>
Now, this works great for the built-in Seam components, but what about user components? There are two options.
- First, Seam supports mixing the two models, allowing the use of the generic <literal><component></literal>
- declarations for user components, along with namespaced declarations for built-in components. But even better,
- Seam allows you to quickly declare namespaces for your own components.
+ Firstly, Seam supports mixing the two models, allowing the use of the generic <literal><component></literal>
+ declarations for user components, along with namespaced declarations for built-in components. Secondly, Seam allows you to quickly declare namespaces for your own components.
</para>

<para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11669 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T23:35:44Z

Author: laubai
Date: 2009-11-24 02:35:44 -0500 (Tue, 24 Nov 2009)
New Revision: 11669

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml
Log:
Edited Security chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-24 07:14:11 UTC (rev 11668)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-24 07:35:44 UTC (rev 11669)
@@ -41,7 +41,7 @@
</para>

<para>
- If on the other hand, your application requires security checks based on contextual state or complex business rules,
+ If, on the other hand, your application requires security checks based on contextual state or complex business rules,
then you will require the features provided by the advanced mode.
</para>
</section>
@@ -112,7 +112,7 @@
<para>
The authentication features provided by Seam Security are built upon JAAS (Java Authentication and Authorization Service),
and as such provide a robust and highly configurable API for handling user authentication. However, for less complex
- authentication requirements Seam offers a much more simplified method of authentication that hides the complexity of JAAS.
+ authentication requirements Seam offers a simpler authentication method that hides the complexity of JAAS.
</para>

<section>
@@ -324,7 +324,7 @@

<para>
To prevent users from receiving the default error page in response to a security error, it's recommended that
- <literal>pages.xml</literal> is configured to redirect security errors to a more "pretty" page. The two
+ <literal>pages.xml</literal> is configured to redirect security errors to a more attractive page. The two
main types of exceptions thrown by the security API are:
</para>

@@ -394,8 +394,8 @@
</pages>]]></programlisting>

<para>
- (This is less of a blunt instrument than the exception handler shown above, but should
- probably be used in conjunction with it.)
+ This is more refined than the previous exception handler, but should
+ probably be used in conjunction with it.
</para>

<para>
@@ -1045,8 +1045,7 @@

<para>
So how does the security API know whether a user has the <literal>customer:modify</literal> permission
- for a specific customer? Seam Security provides quite a novel method for determining user permissions,
- based on JBoss Rules. A couple of the advantages of using a rule engine are 1) a centralized location
+ for a specific customer? Seam Security determines permissions based on JBoss Rules. Some advantages of using a rule engine are 1) a centralized location
for the business logic that is behind each user permission, and 2) speed - JBoss Rules uses very efficient
algorithms for evaluating large numbers of complex rules involving multiple conditions.
</para>
@@ -1146,9 +1145,9 @@
<programlisting><![CDATA[c: PermissionCheck(name == "customer", action == "delete")]]></programlisting>

<para>
- In plain english, this condition is stating that there must exist a <literal>PermissionCheck</literal> object
+ This condition specifies that a <literal>PermissionCheck</literal> object
with a <literal>name</literal> property equal to "customer", and an <literal>action</literal> property equal
- to "delete" within the working memory.
+ to "delete" must exist within the working memory.
</para>

<para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11668 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T23:14:12Z

Author: laubai
Date: 2009-11-24 02:14:11 -0500 (Tue, 24 Nov 2009)
New Revision: 11668

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml
Log:
Edited Remoting chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml 2009-11-24 07:06:18 UTC (rev 11667)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml 2009-11-24 07:14:11 UTC (rev 11668)
@@ -726,7 +726,7 @@
Javascript if desired. The following example demonstrates how to configure the polling to occur much more
aggressively. You should set these parameters to suitable values for your application: </para>

- <para> Via components.xml: </para>
+ <para> Via <filename>components.xml</filename>: </para>

<programlisting role="XML"><![CDATA[<remoting:remoting poll-timeout="5" poll-interval="1"/>]]></programlisting>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11667 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T23:06:18Z

Author: laubai
Date: 2009-11-24 02:06:18 -0500 (Tue, 24 Nov 2009)
New Revision: 11667

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Dependencies.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Elenhancements.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Framework.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml
Log:
Edited chapters for CP07.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -15,29 +15,18 @@
</para>

<itemizedlist>
- <listitem>
- <para>
- The idea of a <emphasis>workspace</emphasis>, which I
- encountered in a project for the Victorian government in
- 2002. In this project I was forced to implement workspace
- management on top of Struts, an experience I pray never
- to repeat.
+ <listitem>
+ <para>
+ The idea of a <emphasis>workspace</emphasis>.
</para>
- </listitem>
+ </listitem>
<listitem>
<para>
The idea of an <emphasis>application transaction</emphasis>
with optimistic semantics, and the realization that existing
frameworks based around a stateless architecture could not
provide effective management of extended persistence contexts.
- (The Hibernate team is truly fed up with copping the blame for
- <literal>LazyInitializationException</literal>s, which are
- not really Hibernate's fault, but rather the fault of the
- extremely limiting persistence context model supported by
- stateless architectures such as the Spring framework or the
- traditional <emphasis>stateless session facade</emphasis>
- (anti)pattern in J2EE.)
- </para>
+ </para>
</listitem>
<listitem>
<para>
@@ -49,7 +38,7 @@
<para>
By unifying these ideas and providing deep support in the framework,
we have a powerful construct that lets us build richer and more efficient
- applications with less code than before.
+ applications with less code.
</para>

<section>
@@ -170,7 +159,7 @@
</h:commandLink>]]></programlisting>

<para>
- Note that disabling conversation context propagation is absolutely not the
+ Note that disabling conversation context propagation is not the
same thing as ending the conversation.
</para>

@@ -587,8 +576,8 @@
</quote>
</para>
<para>
- With a natural conversation its really easy to have the user
- rejoin the existing conversation, and pick up where they left
+ With a natural conversation it is easy to have the user
+ rejoin the existing conversation and pick up where they left
off - just have them to rejoin the payForItem conversation
with the itemId as the conversation id.
</para>
@@ -598,28 +587,20 @@
</para>

<para>
- For me this consists of a navigable
- hierarchy (I can navigate by editing the url) and a meaningful
- URL (like this Wiki uses - so don't identify things by random
- ids). For some applications user friendly URLs are less
+ This consists of a navigable
+ hierarchy (which can be navigated by editing the url) and a meaningful
+ URL. For some applications user-friendly URLs are less
important, of course.
</para>

<para>
- With a natural conversations, when you are building your hotel
- booking system (or, of course, whatever your app is) you can
- generate a URL like
+ With a natural conversations you can generate a URL like
<literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal>
(of course, whatever parameter <literal>hotel</literal> maps
to on your domain model must be unique) and with URLRewrite
easily transform this to
http://seam-hotels/book/BestWesternAntwerpen.
</para>
-
- <para>
- Much better!
- </para>
-
</section>
<section>
<title>Creating a natural conversation</title>
@@ -692,7 +673,7 @@

<para>
From here, we can see that invoking the action <literal>#{bidAction.placeBid}</literal>
- from our auction view (by the way, all these examples are taken from the seamBay example in Seam),
+ from our auction view (all examples are taken from the seamBay example in Seam),
that we will be redirected to <literal>/bid.xhtml</literal>, which, as we saw previously,
is configured with the natural conversation <literal>PlaceBid</literal>. The declaration for
our action method looks like this:
@@ -749,7 +730,7 @@
Include one or more of the standard workspace switcher JSP
or facelets fragments in your pages. The standard fragments
support workspace management via a drop down menu, a list
- of conversations, or breadcrumbs.
+ of conversations or breadcrumbs.
</para>
</listitem>
</itemizedlist>
@@ -782,7 +763,7 @@

<para>
Note that if this file is missing, the Seam application will
- continue to work perfectly! The only missing functionality
+ continue to work. The only missing functionality
will be the ability to switch workspaces.
</para>

@@ -833,7 +814,7 @@
<para>
Include the following fragment in your JSP or facelets page
to get a drop-down menu that lets you switch to any
- current conversation, or to any other page of the application:
+ current conversation or to any other page of the application:
</para>

<programlisting role="XHTML"><![CDATA[<h:selectOneMenu value="#{switcher.conversationIdOrOutcome}">
@@ -953,8 +934,8 @@

<para>
Conversational components have one minor limitation: they cannot be used to hold bindings
- to JSF components. (We generally prefer not to use this feature of JSF unless absolutely
- necessary, since it creates a hard dependency from application logic to the view.) On a
+ to JSF components. It is best to not to use this feature unless absolutely necessary
+ as it creates a hard dependency from application logic to the view. On a
postback request, component bindings are updated during the Restore View phase,
before the Seam conversation context has been restored.
</para>
@@ -1029,21 +1010,19 @@
Conversational components don't allow real concurrent access therefore
Seam queues each request to process them serially. This allows each
request to be executed in a deterministic fashion. However, a simple
- queue isn't that great — firstly, if a method is, for some
- reason, taking a very long time to complete, running it over and over
- again whenever the client generates a request is bad idea (potential
- for Denial of Service attacks), and, secondly, AJAX is often to used
- to provide a quick status update to the user, so continuing to run the
- action after a long time isn't useful.
+ queue is not optimal — firstly, if a method is taking a very long
+ time to complete, running it repeatedly whenever the client generates a
+ request creates the potential for Denial of Service attacks), and,
+ secondly, AJAX is often to used to provide a quick status update to the
+ user, so continuing to run the action after a long time is not effective.
</para>

<para>
Therefore, when you are working inside a long running conversation,
Seam queues the action event for a period of time (the concurrent
request timeout); if it can't process the event in time, it creates a
- temporary conversation and prints out a message to the user to let them
- know what's going on. It's therefore very important not to flood the
- server with AJAX events!
+ temporary conversation and prints out a message to the user to inform them.
+ It is therefore important not to flood the server with AJAX events.
</para>

<para>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Dependencies.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Dependencies.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Dependencies.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -907,7 +907,7 @@

<para>
- Maven offers support for transitive dependency management and can be used
+ <application>Maven</application> offers support for transitive dependency management and can be used
to manage the dependencies of your Seam project. You can use Maven Ant
Tasks to integrate Maven into your Ant build, or can use Maven to build and
deploy your project.
@@ -919,8 +919,8 @@
</para>

<para>
- Released versions of Seam are available in http://repository.jboss.org/maven2
- and nightly snapshots are available in http://snapshots.jboss.org/maven2.
+ Released versions of Seam are available in <ulink type="http" url="http://repository.jboss.org/maven2"></ulink>
+ and nightly snapshots are available in <ulink type="http" url="http://snapshots.jboss.org/maven2"></ulink>.
</para>

<para>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Elenhancements.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Elenhancements.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Elenhancements.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -62,14 +62,14 @@
are stored (for example, <literal>hotel.id</literal> and
<literal>user.username</literal>), and evaluated (as value
expressions) when the page is submitted. You can't pass objects as
- parameters!
+ parameters.
</para>

<para>
You must ensure that the parameters are available not only when the
- page is rendered, but also when it is submittedIf the arguments can
+ page is rendered, but also when it is submitted. If the arguments can
not be resolved when the page is submitted the action method will be
- called with <literal>null</literal> arguments!
+ called with <literal>null</literal> arguments.
</para>

<para>
@@ -173,8 +173,7 @@
types are passed in by JSF. In the case of a method binding,
JSF assumes that there are no parameters to pass. With this
extension, we can't know the parameter types until after the
- expression has been evaluated. This has two minor
- consequences:
+ expression has been evaluated. This has two consequences:
</para>

<itemizedlist>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Framework.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Framework.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Framework.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -51,8 +51,7 @@
</framework:entity-home>]]></programlisting>

<para>
- If that looks a bit too much like "programming in XML" for
- your taste, you can use extension instead:
+ If you prefer, you can use extension instead:
</para>

<programlisting role="JAVA"><![CDATA[
@@ -68,8 +67,8 @@
}]]></programlisting>

<para>
- The second approach has one huge advantage: you can easily add
- extra functionality, and override the built-in functionality
+ The second approach has the advantage of allowing you to easily add
+ extra functionality and override the built-in functionality
(the framework classes were carefully designed for extension
and customization).
</para>
@@ -183,9 +182,9 @@
</h:form>]]></programlisting>

<para>
- Usually, it is much nicer to be able to refer to the <literal>Person</literal>
- merely as <literal>person</literal>, so let's make that possible by adding a
- line to <literal>components.xml</literal>:
+ Usually, it is preferable to be able to refer to the <literal>Person</literal>
+ merely as <literal>person</literal>. Adding a line to
+ <literal>components.xml</literal> makes this possible:
</para>

<programlisting role="XML"><![CDATA[<factory name="person"
@@ -262,8 +261,8 @@
</para>

<para>
- Suppose we need to create <literal>Person</literal> entries with their
- nationality initialized. We can do that easily, via configuration:
+ Should we need to create <literal>Person</literal> entries with their
+ nationality initialized, we can do so easily, via configuration:
</para>

<programlisting role="XML"><![CDATA[<factory name="person"
@@ -391,14 +390,13 @@
Person_updated=Person #{person.firstName} #{person.lastName} updated]]></programlisting>

<para>
- This enables internationalization, and keeps your code and configuration clean of
+ This enables internationalization and keeps your code and configuration clean of
presentation concerns.
</para>

<para>
- The final step is to add validation functionality to the page, using
- <literal><s:validateAll></literal> and <literal><s:decorate></literal>,
- but I'll leave that for you to figure out.
+ The final step is to add validation functionality to the page using
+ <literal><s:validateAll></literal> and <literal><s:decorate></literal>.
</para>

</section>
@@ -593,10 +591,6 @@

}]]></programlisting>

- <para>
- As you can see, its not an earthshattering improvement...
- </para>
-
</section>

-</chapter>
\ No newline at end of file
+</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -13,10 +13,6 @@
</para>

<para>
- In short, if you are an Eclipse user, then you'll want JBoss Tools!
- </para>
-
- <para>
JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible
with a few tweaks to get your app running on other application servers.
The changes are much like those described for seam-gen later in this
@@ -57,9 +53,7 @@

<para>
First, enter a name for your new project. For this tutorial, we're
- going to use
- <literal>helloworld</literal>
- .
+ going to use <literal>helloworld</literal>.
</para>

@@ -299,7 +293,7 @@

<para>
Finally, review the package names for your generated beans, and if you
- are happy, click <emphasis>Finish</emphasis>:
+ are satisfied, click <emphasis>Finish</emphasis>:
</para>

<mediaobject>
@@ -367,11 +361,11 @@
</imageobject>
</mediaobject>

- <para>
+

<para>
To start JBoss, and deploy the project, just right click on the server
@@ -391,10 +385,9 @@
</mediaobject>

<para>
- Don't get scared by the XML configuration documents that were generated
- into the project directory. They are mostly standard Java EE stuff, the
- stuff you need to create once and then never look at again, and they
- are 90% the same between all Seam projects.
+ The XML configuration documents generated in the project directory are
+ predominately standard Java EE. They are 90% the same between all Seam
+ projects.
</para>

</section>
@@ -560,10 +553,9 @@

<para>
Then go to <literal>http://localhost:8080/helloworld</literal>. You can
- browse the database, edit existing objects, and create new objects. If
- you look at the generated code, you'll probably be amazed how simple it
- is! Seam was designed so that data access code is easy to write by
- hand, even for people who don't want to cheat by using reverse
+ browse the database, edit existing objects, and create new objects.
+ Seam was designed so that data access code is easy to write by
+ hand, even for people who don't want to use reverse
engineering.
</para>
</section>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Gettingstarted.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -4,21 +4,17 @@
<chapter id="gettingstarted">
<title>Getting started with Seam, using seam-gen</title>

- <para>The Seam distribution includes a command line utility that makes it really easy to set up an Eclipse project,
- generate some simple Seam skeleton code, and reverse engineer an application from a preexisting database.</para>
+ <para>The Seam distribution includes a command line utility that makes it easy to set up an Eclipse project,
+ generate some simple Seam skeleton code and reverse engineer an application from a preexisting database.</para>

- <para>This is the easy way to get your feet wet with Seam, and gives you some ammunition for next time you find
- yourself trapped in an elevator with one of those tedious Ruby guys ranting about how great and wonderful his
- new toy is for building totally trivial applications that put things in databases.</para>
-
- <para>In this release, seam-gen works best for people with JBoss AS. You can use the generated project with other
+ <para>In this release, seam-gen works best for people with JBoss AS. You can use the generated project with other
J2EE or Java EE 5 application servers by making a few manual changes to the project configuration.</para>

<para>You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this tutorial, we want to show you how to
use it in conjunction with Eclipse for debugging and integration testing. If you don't want to install Eclipse,
you can still follow along with this tutorial—all steps can be performed from the command line.</para>

- <para>Seam-gen is basically just a big ugly Ant script wrapped around Hibernate Tools, together with some templates.
+ <para>Seam-gen is basically just an Ant script wrapped around Hibernate Tools together with some templates.
That makes it easy to customize if you need to.</para>

<section>
@@ -44,8 +40,6 @@
<para>If you're running JBoss from the command line, you can configure the JVM options in
<literal>bin/run.conf</literal>.</para>

- <para>If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get
- your first <literal>OutOfMemoryException</literal>.</para>
</section>

<section>
@@ -166,9 +160,11 @@
You can edit this page, or the template, in eclipse, and see the results <emphasis>immediately</emphasis>,
by clicking refresh in your browser.</para>

- <para>Don't get scared by the XML configuration documents that were generated into the project directory. They
- are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they
- are 90% the same between all Seam projects. (They are so easy to write that even seam-gen can do it.)</para>
+ <para>
+ The XML configuration documents generated in the project directory are
+ predominately standard Java EE. They are 90% the same between all Seam
+ projects.
+ </para>

<para>The generated project includes three database and persistence configurations. The
<literal>persistence-test.xml</literal> and
@@ -360,7 +356,7 @@
this may be accomplished by touching the top level deployment descriptor: <literal>application.xml</literal>
for an EAR deployment, or <literal>web.xml</literal> for a WAR deployment.)</para>

- <para>But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean
+ <para>If you want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean
components. To make use of this functionality, you must deploy the JavaBean components into the
<literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader,
instead of by the WAR or EAR classloader.</para>
@@ -369,8 +365,8 @@

<itemizedlist>
<listitem>
- <para>the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing
- this limitation)</para>
+ <para>the components must be JavaBean components, they cannot be EJB3 beans.
+ (This limitation is being worked on.)</para>
</listitem>

<listitem>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml 2009-11-24 06:41:27 UTC (rev 11666)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Remoting.xml 2009-11-24 07:06:18 UTC (rev 11667)
@@ -3,11 +3,9 @@

<chapter id="remoting">
<title>Remoting</title>
- <para> Seam provides a convenient method of remotely accessing components from a web page, using AJAX (Asynchronous
- Javascript and XML). The framework for this functionality is provided with almost no up-front development effort -
- your components only require simple annotating to become accessible via AJAX. This chapter describes the steps
- required to build an AJAX-enabled web page, then goes on to explain the features of the Seam Remoting framework in
- more detail. </para>
+ <para>
+ Seam uses Asynchronous JavaScript and XML (AJAX) to remotely access components from a web page. The framework for this functionality requires very little development effort — you can make your components AJAX-accessible with simple annotations. This chapter describes the steps required to build an AJAX-enabled web page, and explains the Seam Remoting framework in further detail.
+ </para>

<section>
<title>Configuration</title>
@@ -114,15 +112,13 @@
// ]]>]]><![CDATA[
</script>]]></programlisting>

- <para> We're done! Deploy your application and browse to your page. Click the button, and enter a name when
- prompted. A message box will display the hello message confirming that the call was successful. If you want to
- save some time, you'll find the full source code for this Hello World example in Seam's
- <literal>/examples/remoting/helloworld</literal> directory. </para>
+ <para>
+ Now deploy your application and browse to your page. Click the button, and enter a name when prompted. A message box will display the "Hello" message, confirming the call's success. (You can find the full source code for this Hello World example in Seam's <filename>/examples/remoting/helloworld</filename> directory.)
+ </para>

- <para> So what does the code of our script actually do? Let's break it down into smaller pieces. To start with,
- you can see from the Javascript code listing that we have implemented two methods - the first method is
- responsible for prompting the user for their name and then making a remote request. Take a look at the following
- line: </para>
+ <para>
+ You can see from the JavaScript code listing that we have implemented two methods. The first method prompts the user for their name, and makes a remote request. Look at the following line:
+ </para>

<programlisting role="XHTML">Seam.Component.getInstance("helloAction").sayHello(name, sayHelloCallback);</programlisting>

@@ -131,16 +127,13 @@
against this stub, which is exactly what happens with the remainder of the line: <literal>sayHello(name,
sayHelloCallback);</literal>. </para>

- <para> What this line of code in its completeness does, is invoke the <literal>sayHello</literal> method of our
- component, passing in <literal>name</literal> as a parameter. The second parameter,
- <literal>sayHelloCallback</literal> isn't a parameter of our component's <literal>sayHello</literal> method,
- instead it tells the Seam Remoting framework that once it receives the response to our request, it should pass
- it to the <literal>sayHelloCallback</literal> Javascript method. This callback parameter is entirely optional,
- so feel free to leave it out if you're calling a method with a <literal>void</literal> return type or if you
- don't care about the result. </para>
+ <para>
+ The whole line invokes the <literal>sayHello</literal> method of our component, passing in name as a parameter. The second parameter, <literal>sayHelloCallback</literal>, is not a parameter of our component's <literal>sayHello</literal> method — it tells the Seam Remoting framework that, once a response to the request is received, the response should be passed to the <literal>sayHelloCallback</literal> JavaScript method. (This callback parameter is optional; you can leave it out if you are calling a method with a void return type, or if the result of the request is not important.)
+ </para>

- <para> The <literal>sayHelloCallback</literal> method, once receiving the response to our remote request then pops
- up an alert message displaying the result of our method call. </para>
+ <para>
+ When the sayHelloCallback method receives the response to our remote request, it displays an alert message with the result of our method call.
+ </para>

</section>

@@ -243,10 +236,9 @@
<section>
<title>Seam.Remoting.createType()</title>

- <para> If your application contains or uses Javabean classes that aren't Seam components, you may need to create
- these types on the client side to pass as parameters into your component method. Use the
- <literal>createType()</literal> method to create an instance of your type. Pass in the fully qualified Java
- class name as a parameter: </para>
+ <para>
+ If your application contains or uses JavaBean classes that are not Seam components, you may need to create these types on the client side to pass as parameters into your component method. Use the <methodname>createType()</methodname> method to create an instance of your type. Pass in the fully-qualified Java class name as a parameter:
+ </para>

<programlisting role="XHTML">var widget = Seam.Remoting.createType("com.acme.widgets.MyWidget");</programlisting>
</section>
@@ -313,12 +305,9 @@
stubs are behavioural, and are used to execute methods against your session bean components, while type stubs
contain state and represent the types that can be passed in as parameters or returned as a result. </para>

- <para> The type of client stub that is generated depends on the type of your Seam component. If the component is a
- session bean, then an executable stub will be generated, otherwise if it's an entity or JavaBean, then a type stub
- will be generated. There is one exception to this rule; if your component is a JavaBean (ie it is not a session
- bean nor an entity bean) and any of its methods are annotated with @WebRemote, then an executable stub will be
- generated for it instead of a type stub. This allows you to use remoting to call methods of your JavaBean
- components in a non-EJB environment where you don't have access to session beans. </para>
+ <para>
+ The type of stub that is generated depends upon the type of your Seam component. If the component is a session bean, an executable stub will be generated. If it is an entity or JavaBean, a type stub will be generated. However, if your component is a JavaBean and any of its methods are annotated with <literal>@WebRemote</literal>, an executable stub will be generated. This lets you call your JavaBean component's methods in a non-EJB environment, where you do not have access to session beans.
+ </para>

</section>

@@ -337,19 +326,16 @@
call <literal>Seam.Remoting.getContext().getConversationId()</literal>. To set the conversation ID before making a
request, call <literal>Seam.Remoting.getContext().setConversationId()</literal>. </para>

- <para> If the conversation ID hasn't been explicitly set with
- <literal>Seam.Remoting.getContext().setConversationId()</literal>, then it will be automatically assigned the
- first valid conversation ID that is returned by any remoting call. If you are working with multiple conversations
- within your page, then you may need to explicitly set the conversation ID before each call. If you are working
- with just a single conversation, then you don't need to do anything special. </para>
+ <para>
+ If the conversation ID has not been explicitly set with Seam.Remoting.getContext().setConversationId(), then the first valid conversation ID returned by any remoting call is assigned automatically. If you are working with multiple conversations within your page, you may need to set your conversation ID explicitly before each call. Single conversations do not require explicit ID setting.
+ </para>
</section>
<section>
<title>Remote calls within the current conversation scope</title>

- <para> In some circumstances it may be required to make a remote call within the scope of the
- current view's conversation. To do this, you must explicitly set the conversation ID to that
- of the view before making the remote call. This small snippet of JavaScript will set the
- conversation ID that is used for remoting calls to the current view's conversation ID: </para>
+ <para>
+ Under some circumstances, you may need to make a remote call within the scope of the current view's conversation. To do so, you must explicitly set the conversation ID to that of the view before making the remote call. The following JavaScript will set the conversation ID being used for remote calls to the current view's conversation ID:
+ </para>

<programlisting role="XHTML"><![CDATA[Seam.Remoting.getContext().setConversationId( #{conversation.id} );]]></programlisting>
</section>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11666 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T22:41:28Z

Author: laubai
Date: 2009-11-24 01:41:27 -0500 (Tue, 24 Nov 2009)
New Revision: 11666

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Persistence.xml
Log:
Edited Persistence chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Persistence.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Persistence.xml 2009-11-24 05:55:24 UTC (rev 11665)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Persistence.xml 2009-11-24 06:41:27 UTC (rev 11666)
@@ -13,28 +13,26 @@
<title>Introduction</title>

<para>
- Seam grew out of the frustration of the Hibernate team with the
- statelessness typical of the previous generation of Java application
- architectures. The state management architecture of Seam was originally
- designed to solve problems relating to persistence—in particular
- problems associated with <emphasis>optimistic transaction processing</emphasis>.
- Scalable online applications always use optimistic transactions. An atomic
- (database/JTA) level transaction should not span a user interaction unless
- the application is designed to support only a very small number of concurrent
- clients. But almost all interesting work involves first displaying data
- to a user, and then, slightly later, updating the same data. So Hibernate was
- designed to support the idea of a persistence context which spanned an
- optimistic transaction.
+
+ Seam was created because of frustration with the statelessness typical of the
+ previous generation of Java application architectures. Seam's state management
+ architecture was originally designed to solve problems relating to persistence,
+ particularly problems associated with optimistic transaction processing. Scalable
+ online applications always use optimistic transactions. An atomic (database/JTA)
+ level transaction should not span a user interaction unless the application is
+ designed to support only a very small number of concurrent clients. But almost all
+ work involves first displaying data to a user, and then updating that data.
+ Hibernate was designed to support a persistence context that spanned an optimistic
+ transaction.
</para>

<para>
- Unfortunately, the so-called "stateless" architectures that preceded Seam and
- EJB 3.0 had no construct for representing an optimistic transaction. So, instead,
- these architectures provided persistence contexts scoped to the atomic
- transaction. Of course, this resulted in many problems for users, and is the
- cause of the number one user complaint about Hibernate: the dreaded
- <literal>LazyInitializationException</literal>. What we need is a construct
- for representing an optimistic transaction in the application tier.
+ Unfortunately, the "stateless" architectures that preceded Seam and EJB3 had no
+ construct to represent an optimistic transaction. Instead, these architectures
+ provided persistence contexts scoped to the atomic transaction. This resulted in
+ many problems for users, and causes the number one user complaint: Hibernate's
+ <exceptionname>LazyInitializationException</exceptionname>. A construct was
+ required to represent an optimistic transaction in the application tier.
</para>

<para>
@@ -42,15 +40,14 @@
component (a stateful session bean) with an <emphasis>extended persistence
context</emphasis> scoped to the lifetime of the component. This is a
partial solution to the problem (and is a useful construct in and of
- itself) however there are two problems:
+ itself), but there are still two issues with this approach:
</para>

<itemizedlist>
<listitem>
<para>
The lifecycle of the stateful session bean must be managed manually
- via code in the web tier (it turns out that this is a subtle problem
- and much more difficult in practice than it sounds).
+ via code in the web tier.
</para>
</listitem>
<listitem>
@@ -62,16 +59,15 @@
</itemizedlist>

<para>
- Seam solves the first problem by providing conversations, and stateful
- session bean components scoped to the conversation. (Most conversations
- actually represent optimistic transactions in the data layer.) This is
- sufficient for many simple applications (such as the Seam booking
- demo) where persistence context propagation is not needed. For more
- complex applications, with many loosly-interacting components in each
- conversation, propagation of the persistence context across components
- becomes an important issue. So Seam extends the persistence context
- management model of EJB 3.0, to provide conversation-scoped extended
- persistence contexts.
+ Seam solves the first problem by providing conversations, and scoping stateful
+ session bean components to the conversation. (Most conversations actually
+ represent optimistic transactions in the data layer.) This is sufficient for many
+ simple applications where persistence context propagation is not required, such as
+ the Seam booking example application. For more complex applications, with many
+ loosely-interacting components in each conversation, propagation of the
+ persistence context across components becomes an important issue. Therefore, Seam
+ extends the persistence context management model of EJB3, to provide conversation-
+ scoped extended persistence contexts.
</para>

</section>
@@ -79,96 +75,93 @@
<section id="persistence.seam-managed-transactions">
<title>Seam managed transactions</title>
<para>
- EJB session beans feature declarative transaction management. The EJB container is able
- to start a transaction transparently when the bean is invoked, and end it when the
- invocation ends. If we write a session bean method that acts as a JSF action listener,
- we can do all the work associated with that action in one transaction, and be sure that
- it is committed or rolled back when we finish processing the action. This is a great feature,
- and all that is needed by some Seam applications.
+ EEJB session beans feature declarative transaction management. The EJB
+ container can start a transaction transparently when the bean is invoked, and
+ end it when the invocation ends. If we write a session bean method that acts
+ as a JSF action listener, all work associated with that action can be
+ performed as one transaction, and committed or rolled back when the action is
+ completely processed. This is a useful feature, and for some Seam
+ applications, this is all that is required.
</para>

<para>
- However, there is a problem with this approach. A Seam application may not perform all data
- access for a request from a single method call to a session bean.
+ However, there is a problem with this approach: in a request from a single
+ method call to a session bean, a Seam application may not perform all data
+ access.
</para>

<itemizedlist>
<listitem>
<para>
- The request might require processing by several loosly-coupled components, each
- of which is called independently from the web layer. It is common to see several
- or even many calls per request from the web layer to EJB components in Seam.
+ when the request requires processing by several loosely-coupled
+ components, with each component being called independently from the
+ web layer. It is common to see multiple calls per request from the web
+ layer to EJB components in Seam.
</para>
</listitem>
<listitem>
<para>
- Rendering of the view might require lazy fetching of associations.
+ when view rendering requires lazily-fetched associations.
</para>
</listitem>
</itemizedlist>

<para>
- The more transactions per request, the more likely we are to encounter atomicity
- and isolation problems when our application is processing many concurrent requests.
- Certainly, all write operations should occur in the same transaction!
+ The more transactions that exist per request, the more likely we are to
+ encounter atomicity and isolation problems while our application processes
+ many concurrent requests. All write operations should occur in the same
+ transaction.
</para>

<para>
- Hibernate users developed the <emphasis>"open session in view"</emphasis> pattern to work
- around this problem. In the Hibernate community, "open session in view" was historically
- even more important because frameworks like Spring use transaction-scoped persistence contexts.
- So rendering the view would cause <literal>LazyInitializationException</literal>s when
- unfetched associations were accessed.
+ To work around this problem, Hibernate users developed the <emphasis>open
+ session in view</emphasis> pattern. This is also important because some
+ frameworks (Spring, for example) use transaction-scoped persistence contexts,
+ which caused <exceptionname>LazyInitializationException</exceptionname>s when
+ unfetched associations were accessed.
</para>

<para>
- This pattern is usually implemented as a single transaction which spans the entire request.
- There are several problems with this implementation, the most serious being that we
- can never be sure that a transaction is successful until we commit it—but by the
- time the "open session in view" transaction is committed, the view is fully rendered, and
- the rendered response may already have been flushed to the client. How can we notify the
- user that their transaction was unsuccessful?
+ <emphasis>Open session in view</emphasis> is usually implemented as a single
+ transaction that spans the entire request. The most serious problem with this
+ implementation is that we cannot be certain that a transaction is successful
+ until we commit it — but when the transaction commits, the view is fully
+ rendered, and the rendered response may already be synchronized the client, so
+ there is no way to notify the user that their transaction did not succeed.
</para>

<para>
- Seam solves both the transaction isolation problem and the association fetching problem,
- while working around the problems with "open session in view". The solution comes in two
- parts:
+ Seam solves the problems with transaction isolation and association fetching,
+ while working around the major flaw in <emphasis>open session in
+ view</emphasis>, with two changes:
</para>

<itemizedlist>
<listitem>
<para>
- use an extended persistence context that is scoped to the conversation,
- instead of to the transaction
+ Seam uses an extended persistence context that is scoped to the
+ conversation instead of the transaction.
</para>
</listitem>
<listitem>
<para>
- use two transactions per request; the first spans the beginning of the restore view
- phase (some transaction managers begin the transaction later at the beginning of the
- apply request vaues phase) until the end of the invoke application phase; the second spans the
- render response phase
+ Seam uses two transactions per request. The first spans from the
+ beginning of the restore view phase until the end of the invoke
+ application phase; the second spans the length of the render response
+ phase. (In some applications, the first phase will begin later, at the
+ beginning of the apply request values phase.)
</para>
</listitem>
</itemizedlist>

<para>
- In the next section, we'll tell you how to set up a conversation-scope persistence
- context. But first we need to tell you how to enable Seam transaction management.
- Note that you can use conversation-scoped persistence contexts without Seam
- transaction management, and there are good reasons to use Seam transaction management
- even when you're not using Seam-managed persistence contexts. However, the two
- facilities were designed to work together, and work best when used together.
+ The next section takes you through the setup of a conversation-scoped
+ persistence context. Before this, we will enable Seam transaction management.
+ You can use conversation-scoped persistence contexts without Seam transaction
+ management, and Seam transaction management is useful even without Seam-
+ managed persistence contexts, but they work most effectively together.
</para>

- <para>
- Seam transaction management is useful even if you're using EJB 3.0
- container-managed persistence contexts. But it is especially useful
- if you use Seam outside a Java EE 5 environment, or in any other
- case where you would use a Seam-managed persistence context.
- </para>
-
<section>
<title>Disabling Seam-managed transactions</title>

@@ -197,7 +190,7 @@
<programlisting role="XML"><![CDATA[<transaction:ejb-transaction />]]></programlisting>

<para>
- However, if you are working in a non EE 5 container, Seam will try auto detect the transaction
+ However, if you are working in a non EE 5 container, Seam will try to auto detect the transaction
synchronization mechanism to use. However, if Seam is unable to detect the correct transaction
synchronization to use, you may find you need configure one of the following:
</para>
@@ -234,23 +227,23 @@
</listitem>
</itemizedlist>
<para>
- Configure JPA RESOURCE_LOCAL transaction management by adding the following to your components.xml where
+ Configure JPA RESOURCE_LOCAL transaction management by adding the following to your <filename>components.xml</filename> where
<literal>#{em}</literal>
is the name of the
<literal>persistence:managed-persistence-context</literal>
component. If your managed persistence context is named <literal>entityManager</literal>, you can
opt to leave out the <literal>entity-manager</literal> attribute. (see
- <xref linkend="persistence.seam-managed-persistence-contexts"/>Seam-managed persistence contexts)
+ <xref linkend="persistence.seam-managed-persistence-contexts"/>.)
</para>
<programlisting role="XML"><![CDATA[<transaction:entity-transaction entity-manager="#{em}"/>]]></programlisting>
<para>
- To configure Hibernate managed transactions declare the following in your components.xml where
+ To configure Hibernate managed transactions declare the following in your <filename>components.xml</filename> where
<literal>#{hibernateSession}</literal>
is the name of the project's
<literal>persistence:managed-hibernate-session</literal>
component. If your managed hibernate session is named <literal>session</literal>, you can
- opt to leave out the <literal>session</literal> attribute. (see
- <xref linkend="persistence.seam-managed-persistence-contexts"/>Seam-managed persistence contexts)
+ opt to leave out the <literal>session</literal> attribute. (See
+ <xref linkend="persistence.seam-managed-persistence-contexts"/>.)
</para>
<programlisting role="XML"><![CDATA[<transaction:hibernate-transaction session="#{hibernateSession}"/>]]></programlisting>
<para>
@@ -259,8 +252,7 @@
<programlisting role="XML"><![CDATA[<transaction:no-transaction />]]></programlisting>
<para>
For configuring Spring managed transactions see
- <xref linkend="spring-transactions"/>using Spring PlatformTransactionManagement.
- .
+ <xref linkend="spring-transactions"/>.
</para>
</section>
<section>
@@ -283,29 +275,24 @@
<title>Seam-managed persistence contexts</title>

<para>
- If you're using Seam outside of a Java EE 5 environment, you can't rely upon the
- container to manage the persistence context lifecycle for you. Even if you are
- in an EE 5 environment, you might have a complex application with many loosly
- coupled components that collaborate together in the scope of a single conversation,
- and in this case you might find that propagation of the persistence context between
- component is tricky and error-prone.
+ If you use Seam outside a Java EE 5 environment, you cannot rely upon the
+ container to manage the persistence context lifestyle. Even within EE 5
+ environments, propagating the persistence context between loosely-coupled
+ components in a complex application can be difficult and error-prone.
</para>

<para>
- In either case, you'll need to use a <emphasis>managed persistence context</emphasis>
- (for JPA) or a <emphasis>managed session</emphasis> (for Hibernate) in your components.
- A Seam-managed persistence context is just a built-in Seam component that manages an
- instance of <literal>EntityManager</literal> or <literal>Session</literal> in the
- conversation context. You can inject it with <literal>@In</literal>.
+ In this case, you will need to use a <emphasis>managed persistence context</emphasis> (for JPA) or a <emphasis>managed session</emphasis> (for Hibernate) in your components. A Seam-managed persistence context is just a built-in Seam component that manages an instance of <literal>EntityManager</literal> or <literal>Session</literal> in the conversation context. You can inject it with <literal>@In</literal>.
+
</para>

<para>
- Seam-managed persistence contexts are extremely efficient in a clustered environment.
- Seam is able to perform an optimization that EJB 3.0 specification does not allow
- containers to use for container-managed extended persistence contexts. Seam supports
- transparent failover of extended persisence contexts, without the need to replicate
- any persistence context state between nodes. (We hope to fix this oversight in the
- next revision of the EJB spec.)
+ Seam-managed persistence contexts are extremely efficient in a clustered
+ environment. Seam can perform optimizations for container-managed persistence
+ contexts that the EJB3 specification does not allow. Seam supports transparent
+ failover of extended persistence contexts, without replicating any persistence
+ context state between nodes. (We hope to add this support to the next revision
+ of the EJB specification.)
</para>

<section>
@@ -381,13 +368,14 @@
<property name="connection.datasource">java:/bookingDatasource</property>
...
</session-factory>]]></programlisting>
-
+ <note>
<para>
- Note that Seam does not flush the session, so you should always enable
- <literal>hibernate.transaction.flush_before_completion</literal> to
- ensure that the session is automatically flushed before the JTA transaction
- commits.
+ Seam does not synchronize the session with the database, so always enable
+ <literal>hibernate.transaction.flush_before_completion</literal> to ensure
+ that the session is automatically synchronized before the JTA transaction
+ commits.
</para>
+ </note>

<para>
We can now have a managed Hibernate <literal>Session</literal> injected into our
@@ -417,17 +405,13 @@
</para>

<para>
- By default, the persistence context is flushed (synchronized with the database)
- at the end of each transaction. This is sometimes the desired behavior. But very
- often, we would prefer that all changes are held in memory and only written to
- the database when the conversation ends successfully. This allows for truly
- atomic conversations. As the result of a truly stupid and shortsighted decision
- by certain non-JBoss, non-Sun and non-Sybase members of the EJB 3.0 expert group,
- there is currently no simple, usable and portable way to implement atomic
- conversations using EJB 3.0 persistence. However, Hibernate provides this feature
- as a vendor extension to the <literal>FlushModeType</literal>s defined by the
- specification, and it is our expectation that other vendors will soon provide
- a similar extension.
+ By default, the persistence context is synchronized with the database
+ (flushed) at the end of each transaction. Sometimes this is desirable, but
+ often we prefer all changes to be held in memory, and only written to the
+ database when the conversation ends successfully. This allows for truly atomic
+ conversations with EJB3 persistence. However, Hibernate provides this feature
+ as a vendor extension to the <literal>FlushModeTypes</literal> defined by the specification. We
+ expect other vendors will soon provide a similar extension.
</para>

<para>
@@ -478,19 +462,11 @@
<title>Using the JPA "delegate"</title>

<para>
- The <literal>EntityManager</literal> interface lets you access a vendor-specific
- API via the <literal>getDelegate()</literal> method. Naturally, the most interesting
- vendor is Hibernate, and the most powerful delegate interface is
- <literal>org.hibernate.Session</literal>. You'd be nuts to use anything else. Trust
- me, I'm not biased at all. If you must use a different JPA provider see
- <xref linkend="alt-jpa-providers"/>Using Alternate JPA Providers.
+ The <literal>EntityManager</literal> interface lets you access a vendor-specific API with the <literal>getDelegate()</literal> method. We recommend using Hibernate as your vendor, and <literal>org.hibernate.Session</literal> as your delegate interface, but if you require a different JPA provider, <xref linkend="alt-jpa-providers"/> for further information.
</para>

<para>
- But regardless of whether you're using Hibernate (genius!) or something else
- (masochist, or just not very bright), you'll almost certainly want to use the
- delegate in your Seam components from time to time. One approach would be the
- following:
+ Regardless of your vendor, there are several approaches to using the delegate in your Seam components. One approach is:
</para>

<programlisting role="JAVA"><![CDATA[@In EntityManager entityManager;
@@ -501,9 +477,7 @@
}]]></programlisting>

<para>
- But typecasts are unquestionably the ugliest syntax in the Java language, so most
- people avoid them whenever possible. Here's a different way to get at the
- delegate. First, add the following line to <literal>components.xml</literal>:
+ If you, like most Java users, would rather avoid using typecasts, you can also access the delegate by adding the following line to <filename>components.xml</filename>:
</para>

<programlisting role="XML"><![CDATA[<factory name="session"
@@ -542,17 +516,19 @@
<programlisting role="JAVA"><![CDATA[User user = em.createQuery("from User where username=:username")
.setParameter("username", user.getUsername())
.getSingleResult();]]></programlisting>
-
+
+ <warning>
<para>
- Of course, you should never, ever write it like this:
+ This should never be written as:
</para>

- <programlisting role="JAVA"><![CDATA[User user = em.createQuery("from User where username=" + user.getUsername()) //BAD!
+ <programlisting role="JAVA"><![CDATA[User user = em.createQuery("from User where username=" + user.getUsername())
.getSingleResult();]]></programlisting>

<para>
- (It is inefficient and vulnerable to SQL injection attacks.)
+ This is inefficient, but more importantly, it is vulnerable to SQL injection attacks.
</para>
+ </warning>

</section>

@@ -560,18 +536,11 @@
<title>Using Hibernate filters</title>

<para>
- The coolest, and most unique, feature of Hibernate is <emphasis>filters</emphasis>.
- Filters let you provide a restricted view of the data in the database. You can find
- out more about filters in the Hibernate documentation. But we thought we'd mention
- an easy way to incorporate filters into a Seam application, one that works especially
- well with the Seam Application Framework.
+ Hibernate's most unique, useful feature is the filter. Filters provide a restricted view of the data in the database. You can find more information in the Hibernate documentation, but this section takes you through one easy, effective method of incorporating filters into Seam.
</para>

<para>
- Seam-managed persistence contexts may have a list of filters defined, which will be
- enabled whenever an <literal>EntityManager</literal> or Hibernate <literal>Session</literal>
- is first created. (Of course, they may only be used when Hibernate is the underlying
- persistence provider.)
+ Seam-managed persistence contexts can have a list of filters defined, which will be enabled whenever an <literal>EntityManager</literal> or Hibernate <literal>Session</literal> is first created. (These can only be used when Hibernate is the underlying persistence provider.)
</para>

<programlisting role="XML"><![CDATA[<persistence:filter name="regionFilter">

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11665 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T21:55:25Z

Author: laubai
Date: 2009-11-24 00:55:24 -0500 (Tue, 24 Nov 2009)
New Revision: 11665

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
Log:
Edited Migration chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 05:27:45 UTC (rev 11664)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 05:55:24 UTC (rev 11665)
@@ -11,13 +11,13 @@
is to create a new project using seam-gen in Seam 2, and migrate your code
across. We recognize that many projects may have extensive customizations
to their project, so we also provide instructions for how to upgrade your
- project in-situ in <xref linkend="migrating.insitu" /> Due to the number
+ project in-situ in <xref linkend="migrating.insitu" />. Due to the number
of changes introduced between Seam 1.2 and Seam 2, this may not always be
a straightforward process!
</para>

<para>
- However you decide to migrate your application, you'll need to alter your
+ However you decide to migrate your application, you will need to alter your
code, as many components have moved. <xref linkend="migrating.general"/>
details those changes.
</para>
@@ -26,7 +26,7 @@
<title>Creating a new project skeleton using seam-gen</title>

<para>
- Start by creating a new skeleton seam project. In your Seam 2
+ Start by creating a new skeleton Seam project. In your Seam 2
directory run:
</para>

@@ -34,7 +34,7 @@

<para>
Customize the defaults as needed. You'll want to set the location of
- JBoss EAP, name your project and select an EAR or WAR as needed; you
+ JBoss Enterprise Application Platform, name your project and select an EAR or WAR as needed; you
can accept the defaults for Java package names (as we aren't going to
use the reverse engineering features of seam-gen); you'll want to set
your JDBC driver, URL, username and password correctly, and configure
@@ -69,13 +69,13 @@
<warning>
<para>
You only need to do this if you are migrating from the community
- edition of Seam, JBoss EAP 4.2 and 4.3 shipped a version of Seam
+ edition of Seam. JBoss Enterprise Application Platform 4.2 and 4.3 shipped a version of Seam
1.2 which used JSF 1.2.
</para>
</warning>

<para>
- Seam 2.0 requires JSF 1.2, and JBoss EAP supports Sun's JSF RI. To
+ Seam 2.0 requires JSF 1.2, and JBoss Enterprise Application Platform supports Sun's JSF RI. To
switch to JSF 1.2, you need to remove the MyFaces listener:
</para>

@@ -117,8 +117,8 @@
</web-app>]]></programlisting>

<para>
- In your Seam 1.2 app you may have specified some Seam specific
- configuration in <literal>web.xml</literal>. First, we'll discuss
+ In your Seam 1.2 application you may have specified some Seam specific
+ configuration in <literal>web.xml</literal>. First, we'll discuss
all the Seam related elements you need in
<literal>web.xml</literal>, not just those that have changed, noting
any changes.
@@ -134,8 +134,7 @@
</listener>]]></programlisting>

<para>
- Modify the Seam master filter (note the package of the class
- changed):
+ Modify the Seam master filter (note the change to the class package):
</para>

<programlisting role="XML"><![CDATA[<filter>
@@ -170,7 +169,7 @@
</servlet-mapping>]]></programlisting>

<para>
- Seam 2 will automatically install RichFaces' Ajax4JSF if it present
+ Seam 2 will automatically install RichFaces Ajax4JSF if it present
in your project so you should make sure the Ajax4JSF filter isn't
declared:
</para>
@@ -295,7 +294,7 @@
</para>

<para>
- For testing, you need the jars in Seam's <literal>lib/test</literal>,
+ For testing, you need the jars in Seam's <literal>lib/test</literal> directory,
the jars in Seam's <literal>lib/</literal> directory, your test
classes and application classes together with the
<literal>bootstrap/</literal> directory in your classpath.
@@ -341,7 +340,7 @@

<important>
<para>
- Don't forget to update the XSD's in <literal>pages.xml</literal> and
+ Don't forget to update the XSDs in <literal>pages.xml</literal> and
<literal>components.xml</literal> to point at the ones for Seam 2.
Just change the suffix from <literal>-1.2.xsd</literal> to
<literal>-2.0.xsd</literal>.
@@ -353,7 +352,7 @@

<para>
Seam's built-in components have undergone a major reorganization
- designed to organize them for easier learning, and to isolate
+ designed to make them easier to learn, and to isolate
dependencies upon particular technologies like JSF into specific
packages.
</para>
@@ -406,13 +405,13 @@
</listitem>
<listitem>
<para>
- The Pageflow component are located in
+ The Pageflow components are located in
<literal>org.jboss.seam.pageflow</literal>
</para>
</listitem>
<listitem>
<para>
- The Pages component are located in
+ The Pages components are located in
<literal>org.jboss.seam.navigation</literal>
</para>
</listitem>
@@ -1047,7 +1046,7 @@
<title>Annotation changes in Seam 2</title>

<para>
- Annotations have also moved to reflect their purpose. In
+ Annotations have also moved to reflect their purpose.
</para>

<itemizedlist>
@@ -1209,7 +1208,7 @@
</listitem>
<listitem>
<para>
- Exception handling annotations moved to
+ Annotations related to exception handling have moved to
<literal>org.jboss.seam.annotations.exception</literal>
</para>
<itemizedlist>
@@ -1284,7 +1283,7 @@

<para>
If you are using jBPM for business processes,
- you need to add the tx service to <literal>jbpm.cfg.xml</literal>:
+ you need to add the <classname>tx</classname> service to <literal>jbpm.cfg.xml</literal>:
</para>

<programlisting role="XML"><![CDATA[<service name="tx" factory="org.jbpm.tx.TxServiceFactory" />]]></programlisting>
@@ -1318,7 +1317,7 @@
to the data picker from your stylesheet to save on unnecessary bandwidth use.
</para>
<para>
- You should check the RichFaces documentation for more information on
+ Check the RichFaces documentation for more information on
parameter name changes and namespace changes.
</para>

@@ -1354,7 +1353,7 @@
<title>Changes to seam-gen</title>

<para>There was a change in seam-gen regarding
- how the generated classes are organized when generate-entities is
+ how generated classes are organized when generate-entities is
executed.</para>

<variablelist>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11664 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T21:27:46Z

Author: laubai
Date: 2009-11-24 00:27:45 -0500 (Tue, 24 Nov 2009)
New Revision: 11664

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Mail.xml
Log:
Edited Mail chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Mail.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Mail.xml 2009-11-24 04:55:22 UTC (rev 11663)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Mail.xml 2009-11-24 05:27:45 UTC (rev 11664)
@@ -1,7 +1,7 @@
<chapter id="mail">
<title>Email</title>
<para>
- Seam now includes an optional components for templating and sending emails.
+ Seam now includes an optional component for templating and sending emails.
</para>

<para>
@@ -11,13 +11,13 @@
</para>

<para>
- The examples/mail project contains an example of the email support in
+ The <filename>examples/mail</filename> project contains an example of the email support in
action. It demonstrates proper packaging, and it contains a number of
example that demonstrate the key features currently supported.
</para>

<para>
- You can also test your mail's using Seam's integration testing environment.
+ You can also test your mail using Seam's integration testing environment.
See <xref linkend="testing.mail" />.
</para>

@@ -26,7 +26,7 @@

<para>
You don't need to learn a whole new templating language to use Seam Mail
- — an email is just facelet!
+ — an email is just a facelet!
</para>

<programlisting role="XHTML"><![CDATA[<m:message xmlns="http://www.w3.org/1999/xhtml"
@@ -90,7 +90,7 @@
<title>Attachments</title>
<para>
Seam makes it easy to attach files to an email. It supports most of
- the standard java types used when working with files.
+ the standard Java types used when working with files.
</para>

<para>
@@ -160,7 +160,7 @@

<para>
You may be wondering what <literal>cid:#{...}</literal> does. Well, the
- IETF specified that by putting this as the src for your image, the
+ IETF specified that by putting this as the <varname>src</varname> for your image, the
attachments will be looked at when trying to locate the image (the
<literal>Content-ID</literal>'s must match) — magic!
</para>
@@ -224,8 +224,7 @@
<title>Templating</title>

<para>
- The mail templating example shows that facelets templating Just Works
- with the Seam mail tags.
+ The mail templating example shows facelets templating working with the Seam mail tags.
</para>

<para>
@@ -258,7 +257,7 @@
You can also use facelets source tags in your email, but you must place
them in a jar in <literal>WEB-INF/lib</literal> - referencing the
<literal>.taglib.xml</literal> from <literal>web.xml</literal> isn't
- reliable when using Seam Mail (if you send your mail asynchrounously
+ reliable when using Seam Mail (if you send your mail asynchronously
Seam Mail doesn't have access to the full JSF or Servlet context, and
so doesn't know about <literal>web.xml</literal> configuration
parameters).
@@ -274,10 +273,10 @@
</section>

<section>
- <title>Internationalisation</title>
+ <title>Internationalization</title>

<para>
- Seam supports sending internationalised messages. By default, the
+ Seam supports sending internationalized messages. By default, the
encoding provided by JSF is used, but this can be overridden on the
template:
</para>
@@ -329,14 +328,14 @@
JBoss AS has a number of limitations (and isn't bundled in some versions)
therefore we recommend using the <literal>mail-ra.rar</literal>
distributed with Seam is recommended (it's in the <literal>extras/</literal>
- directory in the Seam bundle). <literal>mail-ra.rar</literal> should
+ directory in the Seam bundle). <literal>mail-ra.rar</literal> should
be placed in <literal>$JBOSS_HOME/server/default/deploy</literal>; if the
version of JBoss AS you use already has this file, replace it.
</para>

<note>
<title>Technology preview </title>
- <para>Distributed mail-ra.rar in Seam is marked as technology preview, so standard support is not guaranteed.</para>
+ <para>Distributed <literal>mail-ra.rar</literal> in Seam is marked as technology preview, so standard support is not guaranteed.</para>
</note>

@@ -371,10 +370,10 @@
musn't access the persistence context.
</para>

- <para>
+ 

<para>
If you aren't using JBoss AS you can still use <literal>mail-ra.rar</literal>
@@ -428,8 +427,8 @@
The JBossAS <literal>deploy/mail-service.xml</literal> configures a
JavaMail session binding into JNDI. The default service
configuration will need altering for your network.
- <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink>
- describes the service in more detail.
+ 
</para>

<programlisting role="XML"><![CDATA[<components xmlns="http://jboss.com/products/seam/components"
@@ -515,7 +514,7 @@

<para>
Here we've created two users, <literal>duke</literal>, who has two email
- addresses and an administrator with the username <literal>root</literal>.
+ addresses, and an administrator with the username <literal>root</literal>.
</para>

</section>
@@ -580,7 +579,7 @@
<term><m:from></term>
<listitem>
<para>
- Set's the From: address for the email. You can only have one of
+ Sets the From: address for the email. You can only have one of
these per email.
</para>
<itemizedlist>
@@ -603,7 +602,7 @@
<term><m:replyTo></term>
<listitem>
<para>
- Set's the Reply-to: address for the email. You can only have one
+ Sets the Reply-to: address for the email. You can only have one
of these per email.
</para>
<itemizedlist>
@@ -642,7 +641,7 @@
<term><m:cc></term>
<listitem>
<para>
- Add a cc recipient to the email. Use multiple <m:cc> tags
+ Adds a carbon copy (CC) recipient to the email. Use multiple <m:cc> tags
for multiple ccs. This tag can be safely placed inside a iterator
tag such as <ui:repeat>.
</para>
@@ -665,8 +664,8 @@
<term><m:bcc></term>
<listitem>
<para>
- Add a bcc recipient to the email. Use multiple <m:bcc>
- tags for multiple bccs. This tag can be safely placed inside a
+ Add a BCC recipient to the email. Use multiple <m:bcc>
+ tags for multiple BCCs. This tag can be safely placed inside a
repeat tag such as <ui:repeat>.
</para>
<itemizedlist>
@@ -753,7 +752,7 @@
</para>
</listitem>
</itemizedlist>
- <para>If the value attribute is ommitted:</para>
+ <para>If the value attribute is omitted:</para>
<itemizedlist>
<listitem>
<para>
@@ -781,7 +780,7 @@
<listitem>
<para>
<literal>contentType</literal> — Specify the MIME type
- of the attached file
+ of the attached file.
</para>
</listitem>
</itemizedlist>
@@ -799,7 +798,7 @@
<term><m:body></term>
<listitem>
<para>
- Set's the body for the email. Supports an <literal>alternative</literal>
+ Sets the body for the email. Supports an <literal>alternative</literal>
facet which, if an HTML email is generated can contain
alternative text for a mail reader which doesn't support html.
</para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11663 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T20:55:22Z

Author: laubai
Date: 2009-11-23 23:55:22 -0500 (Mon, 23 Nov 2009)
New Revision: 11663

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
Log:
Edited JMS chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24 04:46:42 UTC (rev 11662)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24 04:55:22 UTC (rev 11663)
@@ -9,7 +9,7 @@
</para>

<para>
- But for many usecases, JMS is overkill. Seam layers a simple asynchronous method and event
+ But for many use cases, JMS is overkill. Seam layers a simple asynchronous method and event
facility over your choice of <emphasis>dispatchers</emphasis>:
</para>

@@ -46,8 +46,8 @@
<programlisting role="XML"><![CDATA[<async:timer-service-dispatcher/>]]></programlisting>

<para>
- then your asynchronous tasks will be processed by the container's EJB timer service. If
- you're not familiar with the Timer service, don't worry, you don't need to interact with
+ Your asynchronous tasks will be processed by the container's EJB timer service. If
+ you are not familiar with the Timer service, don't worry, you don't need to interact with
it directly if you want to use asynchronous methods in Seam. The important thing to know
is that any good EJB 3.0 implementation will have the option of using persistent timers,
which gives some guarantee that the tasks will eventually be processed.
@@ -250,7 +250,7 @@
processor.schedulePayment(new Date(), 60*60*1000, cal.getTime(), payment);
]]></programlisting>

- <para>Note that the method returns the <literal>QuartzTriggerHandle</literal> object, which you can use later to stop, pause, and resume the scheduler. The <literal>QuartzTriggerHandle</literal> object is serializable, so you can save it into the database if you need to keep it around for extended period of time.</para>
+ <para>Note that the method returns the <literal>QuartzTriggerHandle</literal> object, which you can use later to stop, pause, and resume the scheduler. The <literal>QuartzTriggerHandle</literal> object is serializable, so you can save it into the database if you need to keep it around for an extended period of time.</para>

<programlisting role="JAVA"><![CDATA[QuartzTriggerHandle handle =
processor.schedulePayment(payment.getPaymentDate(),
@@ -286,7 +286,7 @@
processor.schedulePayment(new Date(), "0 10,44 14 ? 3 WED", payment);
]]></programlisting>

- <para>The <literal>@IntervalBusinessDay</literal> annotation supports invocation on the "nth Business Day" scenario. For instance, the following asynchronous method runs at 14:00 on the 2nd business day of each month. By default, it excludes all weekends and US federal holidays until 2010 from the business days.
+ <para>The <literal>@IntervalBusinessDay</literal> annotation supports invocation on the "nth Business Day" scenario. For instance, the following asynchronous method runs at 14:00 on the second business day of each month. By default, it excludes all weekends and US federal holidays until 2010 from the business days.
</para>

<programlisting role="JAVA"><![CDATA[
@@ -307,7 +307,7 @@
new NthBusinessDay(2, "14:00", WEEKLY), payment);
]]></programlisting>

- <para>The <literal>NthBusinessDay</literal> object contains the configuration of the invocation trigger. You can specify more holidays (e.g., company holidays, non-US holidays etc.) via the <literal>additionalHolidays</literal> property.</para>
+ <para>The <literal>NthBusinessDay</literal> object contains the configuration of the invocation trigger. You can specify more holidays (for example, company holidays, non-US holidays etc.) via the <literal>additionalHolidays</literal> property.</para>

<programlisting role="JAVA"><![CDATA[
public class NthBusinessDay implements Serializable

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11662 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T20:46:44Z

Author: laubai
Date: 2009-11-23 23:46:42 -0500 (Mon, 23 Nov 2009)
New Revision: 11662

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml
Log:
Edited jbpm chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml 2009-11-24 04:28:32 UTC (rev 11661)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml 2009-11-24 04:46:42 UTC (rev 11662)
@@ -5,7 +5,7 @@
JBoss jBPM is a business process management engine for any Java SE or EE
environment. jBPM lets you represent a business process or user
interaction as a graph of nodes representing wait states, decisions,
- tasks, web pages, etc. The graph is defined using a simple, very readable,
+ tasks, web pages, etc. The graph is defined using a simple, very readable
XML dialect called jPDL, and may be edited and visualised graphically using
an eclipse plugin. jPDL is an extensible language, and is suitable for
a range of problems, from defining web application page flow, to traditional
@@ -40,11 +40,11 @@
</itemizedlist>

<para>
- Don't get these two things confused ! They operate at very different levels
+ These two definitions operate at very different levels
or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</emphasis>
and <emphasis>task</emphasis> all refer to a single
interaction with a single user. A business process spans many tasks.
- Futhermore, the two applications of jBPM are totally orthogonal. You can
+ Furthermore, the two applications of jBPM are totally orthogonal. You can
use them together or independently or not at all.
</para>

@@ -145,7 +145,7 @@
</page>]]></programlisting>

<para>
- If you find navigation rules overly verbose, you can return view ids
+ If you find navigation rules overly verbose, you can return view IDs
directly from your action listener methods:
</para>

@@ -242,7 +242,7 @@
constrained set of possible transitions to other states. The stateless
model is an <emphasis>ad hoc</emphasis> model which is suitable to
relatively unconstrained, freeform navigation where the user decides
- where he/she wants to go next, not the application.
+ where they want to go next, not the application.
</para>

<para>
@@ -391,7 +391,7 @@
<programlisting role="JAVA"><![CDATA[@Begin(pageflow="numberguess")
public void begin() { ... }]]></programlisting>

- <para>Alternatively we can start a pageflow using pages.xml:</para>
+ <para>Alternatively we can start a pageflow using <filename>pages.xml</filename>:</para>

<programlisting role="XML"><![CDATA[<page>
<begin-conversation pageflow="numberguess"/>
@@ -400,7 +400,7 @@
<para>
If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal>
phase—during a <literal>@Factory</literal> or <literal>@Create</literal>
- method, for example—we consider ourselves to be already at the page being
+ method, for example — we consider ourselves to be already at the page being
rendered, and use a <literal><start-page></literal> node as the first node
in the pageflow, as in the example above.
</para>
@@ -565,7 +565,7 @@
<section>
<title>Pageflow composition</title>
<para>
- It is possible to compose pageflows and have one pageflow pause
+ It is possible to compose pageflows and have one pageflow
pause while another pageflow executes. The <literal><process-state></literal>
node pauses the outer pageflow, and begins execution of a named
pageflow:
@@ -669,7 +669,7 @@
As jBPM processes are persistent across application restarts,
when using Seam in a production environment you won't want to
install the process definition every time the application starts.
- Therefore, in a production environment, you'll need to deploy
+ Therefore, in a production environment, you will need to deploy
the process to jBPM outside of Seam. In other words, only install
process definitions from <literal>components.xml</literal> when
developing your application.
@@ -710,7 +710,7 @@
<programlisting role="JAVA"><![CDATA[@CreateProcess(definition="todo")
public void createTodo() { ... }]]></programlisting>

- <para>Alternatively we can initiate a business process using pages.xml:</para>
+ <para>Alternatively we can initiate a business process using <filename>pages.xml</filename>:</para>

<programlisting role="XML"><![CDATA[<page>
<create-process definition="todo" />
@@ -803,7 +803,7 @@
<programlisting role="JAVA"><![CDATA[@StartTask
public String start() { ... }]]></programlisting>

- <para>Alternatively we can begin work on a task using pages.xml:</para>
+ <para>Alternatively we can begin work on a task using <filename>pages.xml</filename>:</para>

<programlisting role="XML"><![CDATA[<page>
<start-task />
@@ -824,7 +824,7 @@
<programlisting role="JAVA"><![CDATA[@EndTask(transition="completed")
public String completed() { ... }]]></programlisting>

- <para>Alternatively we can use pages.xml:</para>
+ <para>Alternatively we can use <filename>pages.xml</filename>:</para>

<programlisting role="XML"><![CDATA[<page>
<end-task transition="completed" />

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11661 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T20:28:34Z

Author: laubai
Date: 2009-11-23 23:28:32 -0500 (Mon, 23 Nov 2009)
New Revision: 11661

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Itext.xml
Log:
Edited itext chapters.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Itext.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Itext.xml 2009-11-24 03:47:48 UTC (rev 11660)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Itext.xml 2009-11-24 04:28:32 UTC (rev 11661)
@@ -357,7 +357,7 @@
</listitem>

<listitem>
- <para><literal>style</literal> — The font styles. Any combination of :
+ <para><literal>style</literal> — The font styles. Any combination of:
<literal>NORMAL</literal>, <literal>BOLD</literal>,
<literal>ITALIC</literal>, <literal>OBLIQUE</literal>,
<literal>UNDERLINE</literal>, <literal>LINE-THROUGH</literal></para>
@@ -453,8 +453,8 @@

<listitem>
<para>
- <literal>alignment</literal>— The alignment of the image. (see
- <xref linkend="itext.alignment"/> for possible values) </para>
+ <literal>alignment</literal> — The alignment of the image. (See
+ <xref linkend="itext.alignment"/> for possible values.)</para>

</listitem>
<listitem>
@@ -628,13 +628,13 @@
<listitem>
<para>
<literal>alignment</literal> — The alignment of the header/footer
- box section. (see <xref linkend="itext.alignment"/> for alignment values)</para>
+ box section. (See <xref linkend="itext.alignment"/> for alignment values.)</para>

</listitem>

<listitem>
<para><literal>backgroundColor</literal> — The background color of the
- header/footer box. (see <xref linkend="itext.colors"/> for color values)
+ header/footer box. (See <xref linkend="itext.colors"/> for color values.)
</para>
</listitem>

@@ -646,8 +646,8 @@
header/footer box. Individual border sides can be set using
<literal>borderColorLeft</literal>, <literal>borderColorRight</literal>,
<literal>borderColorTop</literal> and
- <literal>borderColorBottom</literal>.(see <xref linkend="itext.colors"/> for
- color values) </para>
+ <literal>borderColorBottom</literal>. (See <xref linkend="itext.colors"/> for
+ color values.)</para>
</listitem>
<listitem>
<para>
@@ -729,7 +729,7 @@
<para>If the generated document follows a book/article structure, the
<literal>p:chapter</literal> and <literal>p:section</literal> tags can be used to
provide the necessary structure. Sections can only be used inside of chapters, but
- they may be nested arbitrarily deep. Most PDF viewers provide easy navigation
+ they may be nested to an arbitrary depth. Most PDF viewers provide easy navigation
between chapters and sections in a document. </para>

<para>
@@ -743,7 +743,7 @@
<listitem>
<para>
<literal>alignment</literal> — The alignment of the header/footer
- box section. (see <xref linkend="itext.alignment"/> for alignment values)</para>
+ box section. (See <xref linkend="itext.alignment"/> for alignment values.)</para>

</listitem>

@@ -810,7 +810,7 @@
<title>Lists</title>

<para>List structures can be displayed using the <literal>p:list</literal> and <literal>p:listItem</literal>
- tags. Lists may contain arbitrarily-nested sublists. List items may not be used outside of a list. he
+ tags. Lists may contain arbitrarily-nested sublists. List items may not be used outside of a list. The
following document uses the <literal>ui:repeat</literal> tag to to display a list of values retrieved
from a Seam component. </para>

@@ -921,13 +921,13 @@
<listitem>
<para>
<literal>alignment</literal> — The alignment of the header/footer
- box section. (see <xref linkend="itext.alignment"/> for alignment values)</para>
+ box section. (See <xref linkend="itext.alignment"/> for alignment values.)</para>

</listitem>

<listitem>
<para><literal>alignment</literal> — The alignment of the list item.
- (See <xref linkend="itext.alignment"/> for possible values)</para>
+ (See <xref linkend="itext.alignment"/> for possible values.)</para>
</listitem>

@@ -972,8 +972,8 @@
<title>Tables</title>

<para>Table structures can be created using the <literal>p:table</literal> and <literal>p:cell</literal>
- tags. Unlike many table structures, there is no explicit row declaration. If a table has 3 columns, then
- every 3 cells will automatically form a row. Header and footer rows can be declared, and the headers and
+ tags. Unlike many table structures, there is no explicit row declaration. If a table has three columns, then
+ every three cells will automatically form a row. Header and footer rows can be declared, and the headers and
footers will be repeated in the event a table structure spans multiple pages.</para>

@@ -1014,7 +1014,7 @@
<listitem>
<para><literal>widths</literal> — The relative widths of each column.
There should be one value for each column. For example: widths="2 1 1" would
- indicate that there are 3 columns and the first column should be twice the
+ indicate that there are three columns and the first column should be twice the
size of the second and third column.</para>
</listitem>

@@ -1031,7 +1031,7 @@
<listitem>
<para><literal>footerRows</literal> — The number of rows that are
considered to be footer rows. This value is subtracted from the
- <literal>headerRows</literal> value. If document has 2 rows which make
+ <literal>headerRows</literal> value. If document has two rows which make
up the header and one row that makes up the footer,
<literal>headerRows</literal> should be set to 3 and
<literal>footerRows</literal> should be set to 1</para>
@@ -1047,7 +1047,7 @@
<listitem>
<para><literal>horizontalAlignment</literal> — The horizontal
alignment of the table. (See <xref linkend="itext.alignment"/> for possible
- values)</para>
+ values.)</para>
</listitem>

<listitem>
@@ -1165,15 +1165,15 @@

<listitem>
<para><literal>horizontalAlignment</literal> — The horizontal
- alignment of the cell. (see <xref linkend="itext.alignment"/> for possible
- values)</para>
+ alignment of the cell. (See <xref linkend="itext.alignment"/> for possible
+ values.)</para>
</listitem>

<listitem>
<para><literal>verticalAlignment</literal> — The vertical alignment of
- the cell. (see <xref linkend="itext.alignment"/> for possible values)</para>
+ the cell. (See <xref linkend="itext.alignment"/> for possible values.)</para>
</listitem>

@@ -1353,7 +1353,7 @@
<para> The default implementation serves PDF documents from a generic URL,
<literal>/seam-doc.seam</literal>. Many browsers (and users) would prefer to see URLs that contain the
actual PDF name like <literal>/myDocument.pdf</literal>. This capability requires some configuration. To
- serve PDF files, all *.pdf resources should be mapped to the DocumentStoreServlet:</para>
+ serve PDF files, all <filename>*.pdf</filename> resources should be mapped to the DocumentStoreServlet:</para>

<programlisting role="XML"><![CDATA[<servlet>
<servlet-name>Document Store Servlet</servlet-name>
@@ -1375,7 +1375,7 @@
</components>]]></programlisting>

<para> Generated documents are stored in conversation scope and will expire when the conversation ends. At
- that point, references to the document will be invalid. To You can specify a default view to be shown
+ that point, references to the document will be invalid. You can specify a default view to be shown
when a document does not exist using the <literal>error-page</literal> property of the documentStore. </para>
<programlisting role="XML"><![CDATA[<pdf:document-store use-extensions="true" error-page="/pdfMissing.seam" />]]></programlisting>
</section>
@@ -1421,7 +1421,7 @@

<listitem>
<para>
- <literal>borderPaint</literal> — The color of the border, if visible;
+ <literal>borderPaint</literal> — The color of the border, if visible.
</para>
</listitem>
<listitem>
@@ -1448,12 +1448,12 @@

<listitem>
<para>
- <literal>domainGridlinesVisible</literal>— Controls whether or not
+ <literal>domainGridlinesVisible</literal> — Controls whether or not
gridlines for the domain axis are shown on the chart. </para>
</listitem>
<listitem>
<para>
- <literal>domainGridlinePaint</literal>— The color of the domain
+ <literal>domainGridlinePaint</literal> — The color of the domain
gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1486,13 +1486,13 @@

<listitem>
<para>
- <literal>legendItemPaint</literal>— The default color of the text
+ <literal>legendItemPaint</literal> — The default color of the text
labels in the legend. </para>
</listitem>

<listitem>
<para>
- <literal>legendItemBackgoundPaint</literal>— The background color for
+ <literal>legendItemBackgoundPaint</literal> — The background color for
the legend, if different from the chart background color.</para>
</listitem>

@@ -1504,27 +1504,27 @@

<listitem>
<para>
- <literal>plotBackgroundPaint</literal>— The color of the plot
+ <literal>plotBackgroundPaint</literal> — The color of the plot
background.</para>
</listitem>

<listitem>
<para>
- <literal>plotBackgroundAlpha</literal>— The alpha (transparency) level
+ <literal>plotBackgroundAlpha</literal> — The alpha (transparency) level
of the plot background. It should be a number between 0 (completely transparent)
and 1 (completely opaque). </para>
</listitem>

<listitem>
<para>
- <literal>plotForegroundAlpha</literal>— The alpha (transparency) level
+ <literal>plotForegroundAlpha</literal> — The alpha (transparency) level
of the plot. It should be a number between 0 (completely transparent) and 1
(completely opaque). </para>
</listitem>

<listitem>
<para>
- <literal>plotOutlinePaint</literal>— The color of the range gridlines,
+ <literal>plotOutlinePaint</literal> — The color of the range gridlines,
if visible. </para>
</listitem>
<listitem>
@@ -1546,12 +1546,12 @@

<listitem>
<para>
- <literal>rangeGridlinesVisible</literal>— Controls whether or not
+ <literal>rangeGridlinesVisible</literal> — Controls whether or not
gridlines for the range axis are shown on the chart. </para>
</listitem>
<listitem>
<para>
- <literal>rangeGridlinePaint</literal>— The color of the range
+ <literal>rangeGridlinePaint</literal> — The color of the range
gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1566,12 +1566,12 @@
</listitem>
<listitem>
<para>
- <literal>titlePaint</literal>— The color of the chart title text.
+ <literal>titlePaint</literal> — The color of the chart title text.
</para>
</listitem>
<listitem>
<para>
- <literal>titleBackgroundPaint</literal>— The background color around
+ <literal>titleBackgroundPaint</literal> — The background color around
the chart title.</para>
</listitem>
<listitem>
@@ -1620,7 +1620,7 @@

<listitem>
<para>
- <literal>borderPaint</literal> — The color of the border, if visible;
+ <literal>borderPaint</literal> — The color of the border, if visible.
</para>
</listitem>
<listitem>
@@ -1647,18 +1647,18 @@

<listitem>
<para>
- <literal>domainGridlinesVisible</literal>— Controls whether or not
+ <literal>domainGridlinesVisible</literal> — Controls whether or not
gridlines for the domain axis are shown on the chart. </para>
</listitem>
<listitem>
<para>
- <literal>domainGridlinePaint</literal>— The color of the domain
+ <literal>domainGridlinePaint</literal> — The color of the domain
gridlines, if visible. </para>
</listitem>
<listitem>
<para>
<literal>domainGridlineStroke</literal> — The stroke style of the
- domain gridleines, if visible. </para>
+ domain gridlines, if visible. </para>
</listitem>

<listitem>
@@ -1685,13 +1685,13 @@

<listitem>
<para>
- <literal>legendItemPaint</literal>— The default color of the text
+ <literal>legendItemPaint</literal> — The default color of the text
labels in the legend. </para>
</listitem>

<listitem>
<para>
- <literal>legendItemBackgoundPaint</literal>— The background color for
+ <literal>legendItemBackgoundPaint</literal> — The background color for
the legend, if different from the chart background color.</para>
</listitem>

@@ -1703,27 +1703,27 @@

<listitem>
<para>
- <literal>plotBackgroundPaint</literal>— The color of the plot
+ <literal>plotBackgroundPaint</literal> — The color of the plot
background.</para>
</listitem>

<listitem>
<para>
- <literal>plotBackgroundAlpha</literal>— The alpha (transparency) level
+ <literal>plotBackgroundAlpha</literal> — The alpha (transparency) level
of the plot background. It should be a number between 0 (completely transparent)
and 1 (completely opaque). </para>
</listitem>

<listitem>
<para>
- <literal>plotForegroundAlpha</literal>— The alpha (transparency) level
+ <literal>plotForegroundAlpha</literal> — The alpha (transparency) level
of the plot. It should be a number between 0 (completely transparent) and 1
(completely opaque). </para>
</listitem>

<listitem>
<para>
- <literal>plotOutlinePaint</literal>— The color of the range gridlines,
+ <literal>plotOutlinePaint</literal> — The color of the range gridlines,
if visible. </para>
</listitem>
<listitem>
@@ -1745,12 +1745,12 @@

<listitem>
<para>
- <literal>rangeGridlinesVisible</literal>— Controls whether or not
+ <literal>rangeGridlinesVisible</literal> — Controls whether or not
gridlines for the range axis are shown on the chart. </para>
</listitem>
<listitem>
<para>
- <literal>rangeGridlinePaint</literal>— The color of the range
+ <literal>rangeGridlinePaint</literal> — The color of the range
gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1765,12 +1765,12 @@
</listitem>
<listitem>
<para>
- <literal>titlePaint</literal>— The color of the chart title text.
+ <literal>titlePaint</literal> — The color of the chart title text.
</para>
</listitem>
<listitem>
<para>
- <literal>titleBackgroundPaint</literal>— The background color around
+ <literal>titleBackgroundPaint</literal> — The background color around
the chart title.</para>
</listitem>
<listitem>
@@ -1814,120 +1814,120 @@

<listitem>
<para>
- <literal>title</literal>— The chart title text. </para>
+ <literal>title</literal> — The chart title text. </para>
</listitem>
<listitem>
<para>
- <literal>label</literal>— The default label text for pie sections.
+ <literal>label</literal> — The default label text for pie sections.
</para>
</listitem>
<listitem>
<para>
- <literal>legend</literal>— A boolean value indicating whether or not
+ <literal>legend</literal> — A boolean value indicating whether or not
the chart should include a legend. Default value is true </para>
</listitem>
<listitem>
<para>
- <literal>is3D</literal>—A boolean value indicating that the chart
+ <literal>is3D</literal> —A boolean value indicating that the chart
should be rendered in 3D instead of 2D. </para>
</listitem>
<listitem>
<para>
- <literal>labelLinkMargin</literal>— The link margin for labels.
+ <literal>labelLinkMargin</literal> — The link margin for labels.
</para>
</listitem>
<listitem>
<para>
- <literal>labelLinkPaint</literal>— The paint used for the label
+ <literal>labelLinkPaint</literal> — The paint used for the label
linking lines. </para>
</listitem>
<listitem>
<para>
- <literal>labelLinkStroke</literal>— he stroke used for the label
+ <literal>labelLinkStroke</literal> — he stroke used for the label
linking lines. </para>
</listitem>

<listitem>
<para>
- <literal>labelLinksVisible</literal>— A flag that controls whether or
+ <literal>labelLinksVisible</literal> — A flag that controls whether or
not the label links are drawn. </para>
</listitem>
<listitem>
<para>
- <literal>labelOutlinePaint</literal>— The paint used to draw the
+ <literal>labelOutlinePaint</literal> — The paint used to draw the
outline of the section labels. </para>
</listitem>
<listitem>
<para>
- <literal>labelOutlineStroke</literal>— The stroke used to draw the
+ <literal>labelOutlineStroke</literal> — The stroke used to draw the
outline of the section labels. </para>
</listitem>
<listitem>
<para>
- <literal>labelShadowPaint</literal>— The paint used to draw the shadow
+ <literal>labelShadowPaint</literal> — The paint used to draw the shadow
for the section labels. </para>
</listitem>
<listitem>
<para>
- <literal>labelPaint</literal>— The color used to draw the section
- labels </para>
+ <literal>labelPaint</literal> — The color used to draw the section
+ labels. </para>
</listitem>
<listitem>
<para>
- <literal>labelGap</literal>— The gap between the labels and the plot
+ <literal>labelGap</literal> — The gap between the labels and the plot
as a percentage of the plot width. </para>
</listitem>
<listitem>
<para>
- <literal>labelBackgroundPaint</literal>— The color used to draw the
+ <literal>labelBackgroundPaint</literal> — The color used to draw the
background of the section labels. If this is null, the background is not filled.
</para>
</listitem>

<listitem>
<para>
- <literal>startAngle</literal>— The starting angle of the first
+ <literal>startAngle</literal> — The starting angle of the first
section. </para>
</listitem>
<listitem>
<para>
- <literal>circular</literal>— A boolean value indicating that the chart
+ <literal>circular</literal> — A boolean value indicating that the chart
should be drawn as a circle. If false, the chart is drawn as an ellipse. The
default is true. </para>
</listitem>
<listitem>
<para>
- <literal>direction</literal>— The direction the pie section are drawn.
+ <literal>direction</literal> — The direction the pie section are drawn.
One of: <literal>clockwise</literal> or <literal>anticlockwise</literal>. The
default is <literal>clockwise</literal>. </para>
</listitem>
<listitem>
<para>
- <literal>sectionOutlinePaint</literal>— The outline paint for all
+ <literal>sectionOutlinePaint</literal> — The outline paint for all
sections. </para>
</listitem>
<listitem>
<para>
- <literal>sectionOutlineStroke</literal>— The outline stroke for all
+ <literal>sectionOutlineStroke</literal> — The outline stroke for all
sections </para>
</listitem>
<listitem>
<para>
- <literal>sectionOutlinesVisible</literal>— Indicates whether an
+ <literal>sectionOutlinesVisible</literal> — Indicates whether an
outline is drawn for each section in the plot. </para>
</listitem>
<listitem>
<para>
- <literal>baseSectionOutlinePaint</literal>— The base section outline
+ <literal>baseSectionOutlinePaint</literal> — The base section outline
paint. </para>
</listitem>
<listitem>
<para>
- <literal>baseSectionPaint</literal>— The base section paint. </para>
+ <literal>baseSectionPaint</literal> — The base section paint. </para>
</listitem>
<listitem>
<para>
- <literal>baseSectionOutlineStroke</literal>— The base section outline
+ <literal>baseSectionOutlineStroke</literal> — The base section outline
stroke. </para>
</listitem>
</itemizedlist>
@@ -1978,7 +1978,7 @@
-->
<listitem>
<para>
- <literal>seriesPaint</literal> — The color of each item in the series
+ <literal>seriesPaint</literal> — The color of each item in the series.
</para>
</listitem>

@@ -2097,7 +2097,7 @@
<para>
<emphasis>Description</emphasis>
</para>
- <para>The color component declares a color or gradient than can be referenced when drawing
+ <para>The color component declares a color or gradient that can be referenced when drawing
filled shapes. </para>
<para>
<emphasis>Attributes</emphasis>
@@ -2108,7 +2108,7 @@
<listitem>
<para>
<literal>color</literal> — The color value. For gradient colors, this
- the starting color. <xref linkend="itext.colors"/>
+ the starting color. <xref linkend="itext.colors"/>.
</para>
</listitem>
<listitem>
@@ -2207,7 +2207,7 @@
<title>Bar codes</title>
<para>Seam can use iText to generate barcodes in a wide variety of formats. These barcodes can
be embedded in a PDF document or displayed as an image on a web page. Note that
- when used with HTML images, barcodes can not currently display barcode text in the barcode.
+ when used with HTML images, barcodes cannot currently display barcode text in the barcode.
</para>

<informaltable id="itext.barcode">
@@ -2246,17 +2246,17 @@
</listitem>
<listitem>
<para>
- <literal>code</literal>— The value to be encoded by the barcode.
+ <literal>code</literal> — The value to be encoded by the barcode.
</para>
</listitem>
<listitem>
<para>
- <literal>xpos</literal>— For PDFs, the absolute y position of the
+ <literal>xpos</literal> — For PDFs, the absolute y position of the
barcode on the page. </para>
</listitem>
<listitem>
<para>
- <literal>ypos</literal>— For PDFs, the absolute y position of the
+ <literal>ypos</literal> — For PDFs, the absolute y position of the
barcode on the page. </para>
</listitem>
<listitem>
@@ -2266,7 +2266,7 @@
</listitem>
<listitem>
<para>
- <literal>barHeight</literal> — The height of the bars in the barCode
+ <literal>barHeight</literal> — The height of the bars in the barCode.
</para>
</listitem>

@@ -2358,7 +2358,7 @@
</listitem>
<listitem>
<para>
- <literal>height</literal> — ..The height of the component to be rendered. </para>
+ <literal>height</literal> — The height of the component to be rendered. </para>
</listitem>
<listitem>
<para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11660 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T19:47:48Z

Author: laubai
Date: 2009-11-23 22:47:48 -0500 (Mon, 23 Nov 2009)
New Revision: 11660

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml
Log:
Edited groovy, hsearch, i18n chapters.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -5,10 +5,9 @@
<title>Groovy integration</title>

<para>One aspect of JBoss Seam is its RAD (Rapid Application Development) capability. While not synonymous with RAD,
- one interesting tool in this space is dynamic languages. Until recently, choosing a dynamic language was
- required choosing a completely different development platform (a development platform with a set of APIs and a
- runtime so great that you would no longer want to use you old legacy Java [sic] APIs anymore, which would be
- lucky because you would be forced to use those proprietary APIs anyway). Dynamic languages built on top of the
+ one interesting tool in this space is dynamic languages. Until recently, choosing a dynamic language
+ required choosing a completely different development platform with a different set of Java APIs.
+ Dynamic languages built on top of the
Java Virtual Machine, and <ulink url="http://groovy.codehaus.org">Groovy</ulink> in particular broke this
approach in silos.</para>

@@ -46,8 +45,8 @@
<section>
<title>Writing Seam applications in Groovy</title>

- <para>There is not much to say about it. Since a Groovy object is a Java object, you can virtually write any
- Seam component, or any class for what it worth, in Groovy and deploy it. You can also mix Groovy classes and
+ <para>Since a Groovy object is a Java object, you can virtually write any
+ Seam component, or any class, in Groovy and deploy it. You can also mix Groovy classes and
Java classes in the same application.</para>

<section>
@@ -94,7 +93,7 @@
}
}</programlisting>

- <para>Groovy natively support the notion of properties (getter/setter), so there is no need to
+ <para>Groovy natively supports the notion of properties (getter/setter), so there is no need to
explicitly write verbose getters and setters: in the previous example, the hotel class can be
accessed from Java as <code>hotel.getCity()</code>, the getters and setters being generated by the
Groovy compiler. This type of syntactic sugar makes the entity code very concise.</para>
@@ -143,7 +142,7 @@
<section>
<title>seam-gen</title>

- <para>Seam gen has a transparent integration with Groovy. You can write Groovy code in seam-gen backed
+ <para>Seam gen itegrates transparently with Groovy. You can write Groovy code in seam-gen backed
projects without any additional infrastructure requirement. When writing a Groovy entity, simply place
your <filename>.groovy</filename> files in <filename>src/model</filename>. Unsurprisingly, when writing
an action, simply place your <filename>.groovy</filename> files in
@@ -166,10 +165,10 @@
<title>Deploying Groovy code</title>

<para>A Groovy class <emphasis>is</emphasis> a Java class, with a bytecode representation just like a Java
- class. To deploy, a Groovy entity, a Groovy Session bean or a Groovy Seam component, a compilation step
+ class. To deploy a Groovy entity, a Groovy Session bean or a Groovy Seam component, a compilation step
is necessary. A common approach is to use the <literal>groovyc</literal> ant task. Once compiles, a
Groovy class is in no way different than a Java class and the application server will treat them
- equally. Note that this allow a seamless mix of Groovy and Java code.</para>
+ equally. Note that this allows a seamless mix of Groovy and Java code.</para>
</section>

<section>
@@ -183,7 +182,7 @@
incrementally with no need to restart the application (and obviously not the application server either).</para>

<para>Be aware that the native .groovy file deployment suffers the same limitations as the regular Seam
- hotdeployment:</para>
+ hot deployment:</para>

<itemizedlist>
<listitem>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Hsearch.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -7,24 +7,23 @@
<section>
<title>Introduction</title>

- <para>Full text search engines like Apache Lucene™ are a very powerful
+ <para>Full text search engines like Apache Lucene are a very powerful
technology that bring full text and efficient queries to applications.
Hibernate Search, which uses Apache Lucene under the covers, indexes your
domain model with the addition of a few annotations, takes care of the
database / index synchronization and returns regular managed objects that
- are matched by full text queries. Keep in mind, thought, that there are
+ are matched by full text queries. Keep in mind, though, that there are
mismatches that arise when dealing with an object domain model over a text
index (keeping the index up to date, mismatch between the index structure
and the domain model, and querying mismatch). But the benefits of speed
and efficiency far outweigh these limitations.</para>

- <para>Hibernate Search has been designed to integrates nicely and as
+ <para>Hibernate Search has been designed to integrate as
naturally as possible with JPA and Hibernate. As a natural extension,
JBoss Seam provides an Hibernate Search integration.</para>

- <para>Please refer to the <ulink
- url="http://www.hibernate.org/hib_docs/search/reference/en/html_single/">Hibernate
- Search documentation</ulink> for information specific to the Hibernate
+ <para>Please refer to the Hibernate Search documentation provided with this release
+ of JBoss Enterprise Application Platform for information specific to the Hibernate
Search project.</para>

<note>
@@ -60,7 +59,7 @@
</persistence-unit>]]></programlisting>

<para>If you plan to target Hibernate Annotations or EntityManager 3.2.x
- (embedded into JBoss EAP AS 4.3), you also need to configure the
+ (embedded into JBoss Enterprise Application Platform 4.3), you also need to configure the
appropriate event listeners.</para>

<programlisting role="XML"><![CDATA[<persistence-unit name="sample">
@@ -115,10 +114,8 @@
<section>
<title>Usage</title>

- <para>Hibernate Search uses annotations to map entities to a Lucene index,
- check the <ulink
- url="http://www.hibernate.org/hib_docs/search/reference/en/html_single/">reference
- documentation</ulink> for more informations.</para>
+ <para>Hibernate Search uses annotations to map entities to a Lucene index. For more information,
+ see the Hibernate Reference Guide provided with this release.</para>

<para>Hibernate Search is fully integrated with the API and semantic of
JPA / Hibernate. Switching from a HQL or Criteria based query requires

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml 2009-11-24 03:39:31 UTC (rev 11659)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/I18n.xml 2009-11-24 03:47:48 UTC (rev 11660)
@@ -7,21 +7,21 @@
<para>
Seam makes it easy to build internationalized applications. First, let's
walk through all the stages needed to internationalize and localize your
- app. Then we'll take a look at the components Seam bundles.
+ application. Then we'll take a look at the component Seam bundles.
</para>

<section>
- <title>Internationalizing your app</title>
+ <title>Internationalizing your application</title>

<para>
- A JEE application consists of many components and all of them must be
+ A Java EE application consists of many components and all of them must be
configured properly for your application to be localized.
</para>

<para>
Starting at the bottom, the first step is to ensure that your database
- server and client is using the correct character encoding for your
- locale. Normally you'll want to use UTF-8. How to do this is outside
+ server and client uses the correct character encoding for your
+ locale. Normally you will want to use UTF-8. How to do this is outside
the scope of this tutorial.
</para>

@@ -104,8 +104,8 @@
To set the display character encoding, you need to use the
<literal><f:view locale="cs_CZ"/></literal> tag (here we tell
JSF to use the Czech locale). You may want to change the encoding of
- the xml document itself if you want to embed localized strings in the
- xml. To do this alter the encoding attribute in xml declaration
+ the XML document itself if you want to embed localized strings in the
+ XML. To do this alter the encoding attribute in XML declaration
<literal><?xml version="1.0" encoding="UTF-8"?></literal> as
required.
</para>
@@ -129,7 +129,7 @@
<para>Each user login session has an associated instance of
<literal>java.util.Locale</literal> (available to the application as a
component named <literal>locale</literal>). Under normal circumstances,
- you won't need to do any special configuration to set the locale. Seam
+ you will not need to do any special configuration to set the locale. Seam
just delegates to JSF to determine the active locale:</para>

<itemizedlist>
@@ -190,7 +190,7 @@
<para>JSF supports internationalization of user interface labels and
descriptive text via the use of <literal><f:loadBundle /></literal>.
You can use this approach in Seam applications. Alternatively, you can
- take advantage of the Seam <literal> messages</literal> component to
+ take advantage of the Seam <literal>messages</literal> component to
display templated labels with embedded EL expressions.</para>

<section>
@@ -202,9 +202,7 @@
internationalized labels available via this special resource bundle. By
default, the resource bundle used by Seam is named
<literal>messages</literal> and so you'll need to define your labels in
- files named <literal> messages.properties</literal>, <literal>
- messages_en.properties</literal>, <literal>
- messages_en_AU.properties</literal>, etc. These files usually belong in
+ files named <literal>messages.properties</literal>, <literal>messages_en.properties</literal>, <literal>messages_en_AU.properties</literal>, etc. These files usually belong in
the <literal>WEB-INF/classes</literal> directory.</para>

<para>So, in <literal>messages_en.properties</literal>:</para>
@@ -230,7 +228,7 @@

<para>If you want to define a message just for a particular page, you
can specify it in a resource bundle with the same name as the JSF view
- id, with the leading <literal>/</literal> and trailing file extension
+ ID, with the leading <literal>/</literal> and trailing file extension
removed. So we could put our message in <literal>
welcome/hello_en.properties</literal> if we only needed to display the
message on <literal> /welcome/hello.jsp</literal>.</para>
@@ -334,7 +332,9 @@
</theme:available-themes>
</theme:theme-selector></programlisting>

- <para>Note that the first theme listed is the default theme.</para>
+ <note>
+ <para>The first theme listed is the default theme.</para>
+ </note>

<para>Themes are defined in a properties file with the same name as the
theme. For example, the <literal>default</literal> theme is defined as a

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11659 - in modules/trunk/persistence/src/main: java/org/seamframework/persistence and 3 other directories.

2009-11-23T19:39:31Z

Author: sboscarine
Date: 2009-11-23 22:39:31 -0500 (Mon, 23 Nov 2009)
New Revision: 11659

Added:
modules/trunk/persistence/src/main/resources/
modules/trunk/persistence/src/main/resources/META-INF/
modules/trunk/persistence/src/main/resources/META-INF/services/
modules/trunk/persistence/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension
Modified:
modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java
Log:
initial commit

Modified: modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java
===================================================================
--- modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java 2009-11-24 02:42:50 UTC (rev 11658)
+++ modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java 2009-11-24 03:39:31 UTC (rev 11659)
@@ -35,11 +35,6 @@
*/
public class PersistenceContextExtension implements Extension
{
- public PersistenceContextExtension()
- {
- System.out.println("\n\n" + this.getClass() + " was constructed");
- }
-
private Bean<EntityManagerFactory> emfBean;

/**

Added: modules/trunk/persistence/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension
===================================================================
--- modules/trunk/persistence/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension (rev 0)
+++ modules/trunk/persistence/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension 2009-11-24 03:39:31 UTC (rev 11659)
@@ -0,0 +1 @@
+org.seamframework.persistence.PersistenceContextExtension
\ No newline at end of file

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11658 - in modules/trunk/transaction/src/main/java/org: seamframework and 1 other directories.

2009-11-23T18:42:50Z

Author: sboscarine
Date: 2009-11-23 21:42:50 -0500 (Mon, 23 Nov 2009)
New Revision: 11658

Added:
modules/trunk/transaction/src/main/java/org/seamframework/
modules/trunk/transaction/src/main/java/org/seamframework/tx/
modules/trunk/transaction/src/main/java/org/seamframework/tx/EntityTransactionInterceptor.java
modules/trunk/transaction/src/main/java/org/seamframework/tx/Transactional.java
Log:
initial commit

Added: modules/trunk/transaction/src/main/java/org/seamframework/tx/EntityTransactionInterceptor.java
===================================================================
--- modules/trunk/transaction/src/main/java/org/seamframework/tx/EntityTransactionInterceptor.java (rev 0)
+++ modules/trunk/transaction/src/main/java/org/seamframework/tx/EntityTransactionInterceptor.java 2009-11-24 02:42:50 UTC (rev 11658)
@@ -0,0 +1,35 @@
+package org.seamframework.tx;
+
+import javax.enterprise.inject.Any;
+import javax.inject.Inject;
+import javax.interceptor.AroundInvoke;
+import javax.interceptor.Interceptor;
+import javax.interceptor.InvocationContext;
+import javax.persistence.EntityManager;
+
+/**
+ * Declarative JPA EntityTransactions
+ *
+ * @author Gavin King
+ *
+ */
+@Transactional @Interceptor
+public class EntityTransactionInterceptor {
+
+ private @Inject @Any EntityManager em;
+
+ @AroundInvoke
+ public Object aroundInvoke(InvocationContext ic) throws Exception {
+ boolean act = !em.getTransaction().isActive();
+ if (act) em.getTransaction().begin();
+ try {
+ Object result = ic.proceed();
+ if (act) em.getTransaction().commit();
+ return result;
+ }
+ catch (Exception e) {
+ if (act) em.getTransaction().rollback();
+ throw e;
+ }
+ }
+}
\ No newline at end of file

Added: modules/trunk/transaction/src/main/java/org/seamframework/tx/Transactional.java
===================================================================
--- modules/trunk/transaction/src/main/java/org/seamframework/tx/Transactional.java (rev 0)
+++ modules/trunk/transaction/src/main/java/org/seamframework/tx/Transactional.java 2009-11-24 02:42:50 UTC (rev 11658)
@@ -0,0 +1,17 @@
+package org.seamframework.tx;
+
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.TYPE;
+import static java.lang.annotation.RetentionPolicy.RUNTIME;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.Target;
+
+import javax.interceptor.InterceptorBinding;
+
+@Retention(RUNTIME)
+@Target({METHOD, TYPE})
+@Documented
+@InterceptorBinding
+public @interface Transactional {}
\ No newline at end of file

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11657 - modules/trunk/transaction.

2009-11-23T18:25:15Z

Author: sboscarine
Date: 2009-11-23 21:25:15 -0500 (Mon, 23 Nov 2009)
New Revision: 11657

Modified:
modules/trunk/transaction/pom.xml
Log:
commented out references to unresolvable dependencies.

Modified: modules/trunk/transaction/pom.xml
===================================================================
--- modules/trunk/transaction/pom.xml 2009-11-24 02:15:55 UTC (rev 11656)
+++ modules/trunk/transaction/pom.xml 2009-11-24 02:25:15 UTC (rev 11657)
@@ -1,30 +1,30 @@
-<project xmlns="http://maven.apache.org/POM/4.0.0"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+ <modelVersion>4.0.0</modelVersion>
+ d">
<parent>
<artifactId>seam-parent</artifactId>
- <groupId>org.jboss.seam</groupId>
+ <groupId>org.jboss.seam</groupId>
<version>3.0.0-SNAPSHOT</version>
- </parent>
-
- <modelVersion>4.0.0</modelVersion>
+ </parent>
<groupId>org.jboss.seam</groupId>
<artifactId>seam-transaction</artifactId>
<packaging>jar</packaging>
<version>3.0.0-SNAPSHOT</version>
<name>Seam Transaction</name>
-
+
<dependencies>

<dependency>
<groupId>javax.ejb</groupId>
- <artifactId>ejb-api</artifactId>
+ <artifactId>ejb-api</artifactId>
</dependency>

<dependency>
<groupId>javax.persistence</groupId>
<artifactId>persistence-api</artifactId>
- </dependency>
+ </dependency>

<dependency>
<groupId>javax.transaction</groupId>
@@ -37,6 +37,18 @@
</dependency>

<dependency>
+ <groupId>javax.transaction</groupId>
+ <artifactId>jta</artifactId>
+ </dependency>
+
+ <dependency>
+ <groupId>javax.enterprise</groupId>
+ <artifactId>cdi-api</artifactId>
+ </dependency>
+
+ 
+ 
</dependencies>
-
-</project>
+</project>
\ No newline at end of file

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11656 - in modules/trunk/persistence/src/main/java: org and 2 other directories.

2009-11-23T18:15:56Z

Author: sboscarine
Date: 2009-11-23 21:15:55 -0500 (Mon, 23 Nov 2009)
New Revision: 11656

Added:
modules/trunk/persistence/src/main/java/org/
modules/trunk/persistence/src/main/java/org/seamframework/
modules/trunk/persistence/src/main/java/org/seamframework/persistence/
modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java
Log:
initial commit

Added: modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java
===================================================================
--- modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java (rev 0)
+++ modules/trunk/persistence/src/main/java/org/seamframework/persistence/PersistenceContextExtension.java 2009-11-24 02:15:55 UTC (rev 11656)
@@ -0,0 +1,202 @@
+package org.seamframework.persistence;
+
+import java.lang.annotation.Annotation;
+import java.lang.reflect.Type;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.Set;
+
+import javax.enterprise.context.ApplicationScoped;
+import javax.enterprise.context.spi.CreationalContext;
+import javax.enterprise.event.Observes;
+import javax.enterprise.inject.Alternative;
+import javax.enterprise.inject.Any;
+import javax.enterprise.inject.Default;
+import javax.enterprise.inject.spi.AfterBeanDiscovery;
+import javax.enterprise.inject.spi.AnnotatedField;
+import javax.enterprise.inject.spi.Bean;
+import javax.enterprise.inject.spi.BeanManager;
+import javax.enterprise.inject.spi.Extension;
+import javax.enterprise.inject.spi.InjectionPoint;
+import javax.enterprise.inject.spi.ProcessProducer;
+import javax.enterprise.inject.spi.Producer;
+import javax.enterprise.util.AnnotationLiteral;
+import javax.inject.Qualifier;
+import javax.persistence.EntityManager;
+import javax.persistence.EntityManagerFactory;
+import javax.persistence.Persistence;
+import javax.persistence.PersistenceContext;
+
+/**
+ * Support for managed persistence contexts in Java SE environment.
+ *
+ * @author Gavin King
+ *
+ */
+public class PersistenceContextExtension implements Extension
+{
+ public PersistenceContextExtension()
+ {
+ System.out.println("\n\n" + this.getClass() + " was constructed");
+ }
+
+ private Bean<EntityManagerFactory> emfBean;
+
+ /**
+ * For @PersistenceContext producer fields, make a bean for the EMF, then
+ * wrap the producer CDI creates, to get the EM from the EMF bean we made
+ * instead of trying to get it from the Java EE component environment.
+ */
+ void processProducer(@Observes ProcessProducer<?, EntityManager> pp, final BeanManager bm)
+ {
+ if (pp.getAnnotatedMember().isAnnotationPresent(PersistenceContext.class))
+ {
+ if (emfBean == null)
+ {
+ AnnotatedField<?> field = (AnnotatedField<?>) pp.getAnnotatedMember();
+ final String unitName = field.getAnnotation(PersistenceContext.class).unitName();
+ final Class<?> module = field.getJavaMember().getDeclaringClass();
+ final Set<Annotation> qualifiers = new HashSet<Annotation>();
+ for (Annotation ann : field.getAnnotations())
+ {
+ Class<? extends Annotation> annotationType = ann.annotationType();
+ // if ( bm.isQualifier(annotationType)) {
+ if (annotationType.isAnnotationPresent(Qualifier.class))
+ { // work around bug in Weld
+ qualifiers.add(ann);
+ }
+ }
+ if (qualifiers.isEmpty())
+ {
+ qualifiers.add(new AnnotationLiteral<Default>()
+ {
+
+ /** default value. Added only to suppress compiler warnings. */
+ private static final long serialVersionUID = 1L;
+ });
+ }
+ qualifiers.add(new AnnotationLiteral<Any>()
+ {
+
+ /** default value. Added only to suppress compiler warnings. */
+ private static final long serialVersionUID = 1L;
+ });
+ final boolean alternative = field.isAnnotationPresent(Alternative.class);
+ final Set<Type> types = new HashSet<Type>()
+ {
+ /** default value. Added only to suppress compiler warnings. */
+ private static final long serialVersionUID = 1L;
+
+ {
+ add(EntityManagerFactory.class);
+ add(Object.class);
+ }
+ };
+
+ // create a bean for the EMF
+ emfBean = new Bean<EntityManagerFactory>()
+ {
+ public Set<Type> getTypes()
+ {
+ return types;
+ }
+
+ public Class<? extends Annotation> getScope()
+ {
+ return ApplicationScoped.class;
+ }
+
+ public EntityManagerFactory create(CreationalContext<EntityManagerFactory> ctx)
+ {
+ return Persistence.createEntityManagerFactory(unitName);
+ }
+
+ public void destroy(EntityManagerFactory emf, CreationalContext<EntityManagerFactory> ctx)
+ {
+ emf.close();
+ ctx.release();
+ }
+
+ public Class<?> getBeanClass()
+ {
+ return module;
+ }
+
+ public Set<InjectionPoint> getInjectionPoints()
+ {
+ // return Collections.EMPTY_SET;
+ return Collections.emptySet();
+ }
+
+ public String getName()
+ {
+ return null;
+ }
+
+ public Set<Annotation> getQualifiers()
+ {
+ return qualifiers;
+ }
+
+ public Set<Class<? extends Annotation>> getStereotypes()
+ {
+ // return Collections.EMPTY_SET;
+ return Collections.emptySet();
+
+ }
+
+ public boolean isAlternative()
+ {
+ return alternative;
+ }
+
+ public boolean isNullable()
+ {
+ return false;
+ }
+ };
+
+ }
+ else
+ {
+ throw new RuntimeException("Only one EMF per application is supported");
+ }
+
+ Producer<EntityManager> producer = new Producer<EntityManager>()
+ {
+
+ public Set<InjectionPoint> getInjectionPoints()
+ {
+ // return Collections.EMPTY_SET;
+ return Collections.emptySet();
+
+ }
+
+ public EntityManager produce(CreationalContext<EntityManager> ctx)
+ {
+ return getFactory(ctx).createEntityManager();
+ }
+
+ private EntityManagerFactory getFactory(CreationalContext<EntityManager> ctx)
+ {
+ return (EntityManagerFactory) bm.getReference(emfBean, EntityManagerFactory.class, ctx);
+ }
+
+ public void dispose(EntityManager em)
+ {
+ if (em.isOpen()) // work around what I suspect is a bug in Weld
+ em.close();
+ }
+ };
+ pp.setProducer(producer);
+ }
+ }
+
+ /**
+ * Register the EMF bean with the container.
+ */
+ void afterBeanDiscovery(@Observes AfterBeanDiscovery abd)
+ {
+ abd.addBean(emfBean);
+ }
+}
\ No newline at end of file

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11655 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T18:12:52Z

Author: laubai
Date: 2009-11-23 21:12:51 -0500 (Mon, 23 Nov 2009)
New Revision: 11655

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Concepts.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Configuration.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Events.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml
Log:
Commented out visible TODO items for CP07 build.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Concepts.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Concepts.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Concepts.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -15,7 +15,7 @@
Let's start by describing the contexts built in to Seam.
</para>

- <sect1>
+ <section>
<title>Seam contexts</title>
<para> Seam contexts are created and destroyed by the framework. The application does not control context
demarcation via explicit Java API calls. Context are usually implicit. In some cases, however, contexts are
@@ -61,16 +61,16 @@
Let's look at each context in turn.
</para>

- <sect2>
+ <section>
<title>Stateless context</title>
<para>
Components which are truly stateless (stateless session beans, primarily) always live in the
stateless context (this is really a non-context). Stateless components are not very interesting, and are
arguably not very object-oriented. Nevertheless, they are important and often useful.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Event context</title>
<para>
The event context is the "narrowest" stateful context, and is a generalization of the notion of the
@@ -83,9 +83,9 @@
When you invoke a Seam component via RMI, or Seam Remoting, the event context is created and
destroyed just for the invocation.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Page context</title>
<para>
The page context allows you to associate state with a particular instance of a rendered page. You can
@@ -95,9 +95,9 @@
serialized to the client, so this construct is extremely robust with respect to multi-window operation
and the back button.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Conversation context</title>
<para>
The conversation context is a truly central concept in Seam. A <emphasis>conversation</emphasis> is a
@@ -145,9 +145,9 @@
<para>
Alternatively, Seam may be configured to keep conversational state in the client browser.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Session context</title>
<para>
A session context holds state associated with the user login session. While there are some cases
@@ -157,9 +157,9 @@
<para>
In a JSR-168 portal environment, the session context represents the portlet session.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Business process context</title>
<para>
The business process context holds state associated with the long running business process. This
@@ -169,18 +169,18 @@
business process is defined externally using a <emphasis>process definition language</emphasis>, so
there are no special annotations for business process demarcation.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Application context</title>
<para>
The application context is the familiar servlet context from the servlet spec. Application context is
mainly useful for holding static information such as configuration data, reference data or metamodels.
For example, Seam stores its own configuration and metamodel in the application context.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Context variables</title>
<para>
A context defines a namespace, a set of <emphasis>context variables</emphasis>. These work much the
@@ -207,9 +207,9 @@
Usually, however, we obtain components from a context via injection, and put component instances into
a context via outjection.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Context search priority</title>
<para>
Sometimes, as above, component instances are obtained from a particular known scope. Other times, all
@@ -242,9 +242,9 @@
Whenever you access a component by name from a JSF page, a priority search occurs.
</para>

- </sect2>
+ </section>

- <sect2 id="concurrency">
+ <section id="concurrency">
<title>Concurrency model</title>
<para>
Neither the servlet nor EJB specifications define any facilities for managing concurrent requests
@@ -279,11 +279,11 @@
This concurrency model means that AJAX clients can safely use volatile session and conversational
state, without the need for any special work on the part of the developer.
</para>
- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Seam components</title>
<para>
Seam components are POJOs (Plain Old Java Objects). In particular, they are JavaBeans or EJB 3.0
@@ -310,7 +310,7 @@
</listitem>
</itemizedlist>

- <sect2>
+ <section>
<title>Stateless session beans</title>
<para>
Stateless session bean components are not able to hold state across multiple invocations. Therefore,
@@ -334,9 +334,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup
or the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Stateful session beans</title>
<para>
Stateful session bean components are able to hold state not only across multiple invocations of the
@@ -364,9 +364,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup
or the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Entity beans</title>
<para>
Entity beans may be bound to a context variable and function as a seam component. Because entities
@@ -397,9 +397,9 @@
Seam entity bean components may be instantiated using <literal>Component.getInstance()</literal>,
<literal>@In(create=true)</literal> or directly using the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>JavaBeans</title>
<para>
Javabeans may be used just like a stateless or stateful session bean. However, they do not provide
@@ -423,9 +423,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated using the
<literal>new</literal> operator.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Message-driven beans</title>
<para>
Message-driven beans may function as a seam component. However, message-driven beans are called quite
@@ -441,9 +441,9 @@
Message-driven beans are never instantiated by the application. They are instantiated by the EJB
container when a message is received.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Interception</title>
<para>
In order to perform its magic (bijection, context demarcation, validation, etc), Seam must intercept
@@ -476,9 +476,9 @@
</interceptor-binding>
</assembly-descriptor>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Component names</title>
<para>
All seam components need a name. We can assign a name to a component using the
@@ -545,9 +545,9 @@
name by the <literal>components.xml</literal> file included in the Seam jar.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Defining the component scope</title>
<para>
We can override the default scope (context) of a component using the <literal>@Scope</literal>
@@ -566,9 +566,9 @@
<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of possible scopes.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Components with multiple roles</title>
<para>
Some Seam component classes can fulfill more than one role in the system. For example, we often have
@@ -601,9 +601,9 @@
...
}]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Built-in components</title>
<para>
Like many good frameworks, Seam eats its own dogfood and is implemented mostly as a set of built-in
@@ -617,11 +617,11 @@
convenient static <literal>instance()</literal> methods:
</para>
<programlisting role="JAVA"><![CDATA[FacesMessages.instance().add("Welcome back, #{user.name}!");]]></programlisting>
- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Bijection</title>
<para>
<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</emphasis> is by now a familiar
@@ -795,9 +795,9 @@
...
}]]></programlisting>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Lifecycle methods</title>

<para>
@@ -831,9 +831,9 @@
specifying <literal>@Startup(depends={....})</literal>.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Conditional installation</title>

<para>
@@ -949,9 +949,9 @@
use it in your application.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Logging</title>

<para>
@@ -1024,9 +1024,9 @@
classpath, Seam with use it. If it is not, Seam will use JDK logging.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal></title>
<para>
Many application servers feature an amazingly broken implementation of <literal>HttpSession</literal>
@@ -1128,9 +1128,9 @@
of managing an entity bean instance using a Seam component.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Factory and manager components</title>
<para>
We often need to work with objects that are not Seam components. But we still want to be able to inject
@@ -1240,6 +1240,6 @@
on every access, a consistent view is provided.
</para>

- </sect1>
+ </section>

</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Configuration.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Configuration.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -8,12 +8,12 @@
off by the following sections; you'll never need to type any of this stuff yourself, since you can just copy and
paste from the example applications! </para>

- <sect1>
+ <section>
<title>Basic Seam configuration</title>

<para> First, let's look at the basic configuration that is needed whenever we use Seam with JSF. </para>

- <sect2>
+ <section>
<title>Integrating Seam with JSF and your servlet container</title>

<para> Of course, you need a faces servlet! </para>
@@ -67,9 +67,9 @@
<param-value>true</param-value>
</context-param>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Using facelets</title>

<para> If you want follow our advice and use facelets instead of JSP, add the following lines to
@@ -86,9 +86,9 @@
<param-value>.xhtml</param-value>
</context-param>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Seam Resource Servlet</title>

<para> The Seam Resource Servlet provides resources used by Seam Remoting, captchas (see the security
@@ -104,9 +104,9 @@
<servlet-name>Seam Resource Servlet</servlet-name>
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Seam servlet filters</title>

<para> Seam doesn't need any servlet filters for basic operation. However, there are several features which
@@ -158,7 +158,7 @@

<para> Adding the master filter enables the following built-in filters. </para>

- <sect3>
+ <section>
<title>Exception handling</title>
<para> This filter provides the exception mapping functionality in <literal>pages.xml</literal> (almost
all applications will need this). It also takes care of rolling back uncommitted transactions when
@@ -178,9 +178,9 @@
</components>]]></programlisting>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Conversation propagation with redirects</title>
<para> This filter allows Seam to propagate the conversation context across browser redirects. It
intercepts any browser redirects and adds a request parameter that specifies the Seam conversation
@@ -190,9 +190,9 @@
in <literal>components.xml</literal>: </para>

<programlisting role="XML"><![CDATA[<web:redirect-filter url-pattern="*.seam"/>]]></programlisting>
- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Multipart form submissions</title>
<para> This feature is necessary when using the Seam file upload JSF control. It detects multipart form
requests and processes them according to the multipart/form-data specification (RFC-2388). To
@@ -217,9 +217,9 @@
this value, the request will be aborted. The default setting is 0 (no size limit). </para>
</listitem>
</itemizedlist>
- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Character encoding</title>
<para> Sets the character encoding of submitted form data. </para>

@@ -244,9 +244,9 @@
already specify an encoding. The default setting is <literal>false</literal>. </para>
</listitem>
</itemizedlist>
- </sect3>
+ </section>

- <sect3>
+ <section>
<title>RichFaces</title>

<para>
@@ -292,9 +292,9 @@
</listitem>
</itemizedlist>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Identity Logging</title>

<para>
@@ -312,9 +312,9 @@
<web:logging-filter url-pattern="*.seam"/>
</components>]]></programlisting>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Context management for custom servlets</title>
<para> Requests sent direct to some servlet other than the JSF servlet are not processed through the JSF
lifecycle, so Seam provides a servlet filter that can be applied to any other servlet that needs
@@ -339,9 +339,9 @@
Seam exposes the conversation id as a property of the built in component
<literal>conversation</literal>. </para>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Adding custom filters</title>
<para> Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the
chain your filter is placed (the servlet specification doesn't provide a well defined order if you
@@ -360,10 +360,10 @@
should be further down the chain than the RichFaces filter
(<literal>@Filter(within="org.jboss.seam.web.ajax4jsfFilter")</literal>). </para>

- </sect3>
- </sect2>
+ </section>
+ </section>

- <sect2>
+ <section>
<title>Integrating Seam with your EJB container</title>

<para> We need to apply the <literal>SeamInterceptor</literal> to our Seam components. The simplest way to
@@ -414,9 +414,9 @@

<programlisting role="XML"><![CDATA[<transaction:ejb-transaction/>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Don't forget!</title>

<para> There is one final item you need to know about. You must place a <literal>seam.properties</literal>,
@@ -436,11 +436,11 @@
component explicitly in <literal>components.xml</literal>, just like some other competing frameworks do!
I think you'll like our way better. </para>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1 id="alt-jpa-providers">
+ <section id="alt-jpa-providers">
<title>Using Alternate JPA Providers</title>

<para> Seam comes packaged and configured with Hibernate as the default JPA provider.
@@ -482,9 +482,9 @@
provider needs. Don't forget to package your new provider's jar files in the
application if they are needed.
</para>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configuring Seam in Java EE 5</title>

<mediaobject>
@@ -498,7 +498,7 @@

<para> If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam! </para>

- <sect2>
+ <section>
<title>Packaging</title>

<para> Once you've packaged all this stuff together into an EAR, the archive structure will look something
@@ -564,11 +564,11 @@
only about a third of the way there. If you're too overwhelmed by all this tedious configuration stuff,
feel free to skip over the rest of this section and come back to it later. </para>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configuring Seam in J2EE</title>

<para> Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. In this case you would use
@@ -596,7 +596,7 @@
JavaBeans instead of EJB3, and another version that uses JPA and JavaBeans. These example applications are
ready to deploy into any J2EE application server. </para>

- <sect2>
+ <section>
<title>Boostrapping Hibernate in Seam</title>

<para> Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your
@@ -610,9 +610,9 @@
<programlisting role="XML"><![CDATA[<persistence:managed-hibernate-session name="hibernateSession"
session-factory="#{hibernateSessionFactory}"/>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Boostrapping JPA in Seam</title>

<para> Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your
@@ -626,9 +626,9 @@
<programlisting role="XML"><![CDATA[<persistence:managed-persistence-context name="entityManager"
entity-manager-factory="#{entityManagerFactory}"/>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Packaging</title>

<para> We can package our application as a WAR, in the following structure: </para>
@@ -668,10 +668,10 @@
<para> If we want to deploy Hibernate in a non-EE environment like TestNG, we need to do a little
bit more work. </para>

- </sect2>
- </sect1>
+ </section>
+ </section>

- <sect1>
+ <section>
<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
@@ -685,9 +685,9 @@
<programlisting role="XML"><![CDATA[<transaction:hibernate-transaction session="#{session}"/>]]></programlisting>

<para> Of course, you'll also need to define a datasource.</para>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configuring jBPM in Seam</title>
<para> Seam's jBPM integration is not installed by default, so you'll need to enable jBPM by installing a
built-in component. You'll also need to explicitly list your process and pageflow definitions. In
@@ -732,7 +732,7 @@
<para> The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should
control the JTA transactions. </para>

- <sect2>
+ <section>
<title>Packaging</title>

<para> There is not yet any well-defined packaging format for jBPM configuration and process/pageflow
@@ -782,11 +782,11 @@
approveDocument.jpdl.xml
documentLifecycle.jpdl.xml]]></programlisting>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configuring SFSB and Session Timeouts in JBoss AS</title>

<para> It is very important that the timeout for Stateful Session Beans is set higher than the timeout for HTTP
@@ -829,9 +829,9 @@
<para> To override this value for your own application, simply include this entry in your application's own
<literal>web.xml</literal>. </para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Running Seam in a Portlet</title>

<para>
@@ -847,6 +847,6 @@
<para>Seam Integration with JBoss Portlet Bridge is marked as technology preview, so standard support is not guaranteed.</para>
</note>

- </sect1>
+ </section>

</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Conversations.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -259,10 +259,10 @@
workspace management.
</para>

- <para>
+

<para>
Usually, if a component exists in a parent conversation of the
@@ -1243,4 +1243,4 @@
</itemizedlist>
</section>
</section>
-</chapter>
\ No newline at end of file
+</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Events.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Events.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Events.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -104,10 +104,10 @@
Furthermore, the view id mentioned in the <literal><page></literal>
element need not correspond to a real JSP or Facelets page! So, we can
reproduce the functionality of a traditional action-oriented framework
- like Struts or WebWork using page actions. For example:
+ like Struts or WebWork using page actions.
</para>

- <programlisting><![CDATA[TODO: translate struts action into page action]]></programlisting>
+

<para>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Groovy.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -40,7 +40,7 @@
</listitem>
</itemizedlist>

- <para>TODO: write a quick overview of the Groovy syntax add-on</para>
+
</section>

<section>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -31,7 +31,7 @@
</listitem>
</itemizedlist>

- <sect1>
+ <section>
<title>Asynchronicity</title>

<para>
@@ -69,7 +69,7 @@
same. They can just "plug and play" by adding a line to <literal>components.xml</literal>.
</para>

- <sect2>
+ <section>
<title>Asynchronous methods</title>

<para>
@@ -219,9 +219,9 @@
Asynchronous methods cannot return any other value to the caller.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Asynchronous methods with the Quartz Dispatcher</title>

<para>
@@ -336,9 +336,9 @@

<para>The <literal>@IntervalDuration</literal>, <literal>@IntervalCron</literal>, and <literal>@IntervalNthBusinessDay</literal> annotations are mutually exclusive. If they are used in the same method, a <literal>RuntimeException</literal> will be thrown.</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Asynchronous events</title>
<para>
Component-driven events may also be asynchronous. To raise an event for asynchronous
@@ -349,11 +349,11 @@
Components may observe asynchronous events in the usual way, but remember that only the
business process context is propagated to the asynchronous thread.
</para>
- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Messaging in Seam</title>

<para>
@@ -361,7 +361,7 @@
Seam components.
</para>

- <sect2>
+ <section>
<title>Configuration</title>
<para>
To configure Seam's infrastructure for sending JMS messages,
@@ -395,9 +395,9 @@
auto-create="true"
queue-jndi-name="queue/paymentQueue"/>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Sending messages</title>
<para>
Now, you can inject a JMS <literal>TopicPublisher</literal> and
@@ -438,24 +438,24 @@
}
}]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Receiving messages using a message-driven bean</title>
<para>
You can process messages using any EJB3 message driven bean. Message-driven
beans may even be Seam components, in which case it is possible to inject
other event and application scoped Seam components.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Receiving messages in the client</title>
<para>
Seam Remoting lets you subscribe to a JMS topic from client-side JavaScript. This is
described in <xref linkend="remoting"/>.
</para>
- </sect2>
+ </section>

- </sect1>
+ </section>
</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -8,7 +8,7 @@
for securing both domain and page resources within your Seam project.
</para>

- <sect1>
+ <section>
<title>Overview</title>

<para>
@@ -30,7 +30,7 @@
</listitem>
</itemizedlist>

- <sect2>
+ <section>
<title>Which mode is right for my application?</title>

<para>
@@ -44,10 +44,10 @@
If on the other hand, your application requires security checks based on contextual state or complex business rules,
then you will require the features provided by the advanced mode.
</para>
- </sect2>
- </sect1>
+ </section>
+ </section>

- <sect1>
+ <section>
<title>Requirements</title>

<para>
@@ -79,9 +79,9 @@
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Disabling Security</title>

<para>
@@ -104,9 +104,9 @@
<para>Page restrictions</para>
</listitem>
</itemizedlist>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Authentication</title>

<para>
@@ -115,7 +115,7 @@
authentication requirements Seam offers a much more simplified method of authentication that hides the complexity of JAAS.
</para>

- <sect2>
+ <section>
<title>Configuration</title>

<para>
@@ -151,9 +151,9 @@
to authenticate the user.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Writing an authentication method</title>

<para>
@@ -205,7 +205,7 @@
authentication method returns <literal>false</literal> to indicate the authentication failed.
</para>

- <sect3>
+ <section>
<title>Identity.addRole()</title>

<para>
@@ -228,9 +228,9 @@
</imageobject>
</mediaobject>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Special Considerations</title>

<para>
@@ -257,11 +257,11 @@
userStats.setLastLoginDate(new Date());
userStats.incrementLoginCount();
}]]></programlisting>
- </sect3>
+ </section>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Writing a login form</title>

<para>
@@ -291,9 +291,9 @@
action will clear the security state of the currently authenticated user.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Simplified Configuration - Summary</title>
<para>
So to sum up, there are the three easy steps to configure authentication:
@@ -317,9 +317,9 @@
</listitem>
</itemizedlist>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Handling Security Exceptions</title>

<para>
@@ -375,9 +375,9 @@
Seam includes some special functionality for handling this problem.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Login Redirection</title>

<para>
@@ -420,9 +420,9 @@
the conversation in your <literal>authenticate()</literal> method.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>HTTP Authentication</title>

<para>
@@ -450,7 +450,7 @@
authentication realm that is presented to the user when they authenticate.
</para>

- <sect3>
+ <section>
<title>Writing a Digest Authenticator</title>

<para>
@@ -478,11 +478,11 @@
}
}
]]></programlisting>
- </sect3>
+ </section>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Advanced Authentication Features</title>

<para>
@@ -490,7 +490,7 @@
security requirements.
</para>

- <sect3>
+ <section>
<title>Using your container's JAAS configuration</title>

<para>
@@ -508,13 +508,13 @@
container your Seam application is deployed in. It merely instructs Seam Security to authenticate
itself using the configured JAAS security policy.
</para>
- </sect3>
+ </section>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Error Messages</title>

<para>
@@ -597,9 +597,9 @@
</tbody>
</tgroup>
</table>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Authorization</title>

<para>
@@ -610,7 +610,7 @@
above.
</para>

- <sect2>
+ <section>
<title>Core concepts</title>

<para>
@@ -628,9 +628,9 @@
for example <literal>customer:delete</literal>, or <literal>customer:insert</literal>.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Securing components</title>

<para>
@@ -638,7 +638,7 @@
<literal>@Restrict</literal> annotation.
</para>

- <sect3>
+ <section>
<title>The @Restrict annotation</title>

<para>
@@ -718,9 +718,9 @@
in <literal>Identity</literal>, which in this case can then determine if the user has the required
permission for modifying the specified <literal>Account</literal> object.
</para>
- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Inline restrictions</title>
<para>
Sometimes it might be desirable to perform a security check in code, without using the
@@ -762,10 +762,10 @@
if (!Identity.instance().hasPermission("customer", "create", null))
throw new AuthorizationException("You may not create new customers");]]></programlisting>

- </sect3>
- </sect2>
+ </section>
+ </section>

- <sect2>
+ <section>
<title>Security in the user interface</title>

<para>
@@ -826,9 +826,9 @@
</h:column>
</h:dataTable>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Securing pages</title>
<para>
Page security requires that the application is using a <literal>pages.xml</literal> file, however is
@@ -859,9 +859,9 @@
<literal>admin</literal> role.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Securing Entities</title>

<para>
@@ -990,7 +990,7 @@
your JPA provider.
</para>

- <sect3>
+ <section>
<title>Entity security with JPA</title>

<para>
@@ -1014,9 +1014,9 @@

</entity-mappings>]]></programlisting>

- </sect3>
+ </section>

- <sect3>
+ <section>
<title>Entity security with a Managed Hibernate Session</title>

<para>
@@ -1025,13 +1025,13 @@
need to do anything special to use entity security.
</para>

- </sect3>
+ </section>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Writing Security Rules</title>

<para>
@@ -1040,7 +1040,7 @@
checks are processed, and how to implement permission checks for a Seam application.
</para>

- <sect2>
+ <section>
<title>Permissions Overview</title>

<para>
@@ -1051,9 +1051,9 @@
algorithms for evaluating large numbers of complex rules involving multiple conditions.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Configuring a rules file</title>

<para>
@@ -1083,9 +1083,9 @@
<para>
Once the <literal>RuleBase</literal> component is configured, it's time to write the security rules.
</para>
- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Creating a security rules file</title>
<para>
For this step you need to create a file called <literal>security.drl</literal> in the
@@ -1215,7 +1215,7 @@
intended for.
</para>

- <sect3>
+ <section>
<title>Wildcard permission checks</title>

<para>
@@ -1237,13 +1237,13 @@
This rule allows users with the <literal>admin</literal> role to perform <emphasis>any</emphasis> action for
any <literal>customer</literal> permission check.
</para>
- </sect3>
+ </section>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>SSL Security</title>

<para>
@@ -1299,9 +1299,9 @@
sensitive data from pages using HTTPS to other pages using HTTP.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>CAPTCHA</title>

<para>
@@ -1311,7 +1311,7 @@
prevent automated processes from interacting with your application.
</para>

- <sect2>
+ <section>
<title>Configuring the CAPTCHA Servlet</title>
<para>
To get up and running, it is necessary to configure the Seam Resource Servlet, which will provide the Captcha
@@ -1328,9 +1328,9 @@
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Adding a CAPTCHA to a form</title>

<para>
@@ -1349,9 +1349,9 @@
validated against the CAPTCHA when the form is submitted.
</para>

- </sect2>
+ </section>

- <sect2>
+ <section>
<title>Customising the CAPTCHA algorithm</title>

<para>
@@ -1378,11 +1378,11 @@
}
}]]></programlisting>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Security Events</title>

<para>
@@ -1534,9 +1534,9 @@
</tgroup>
</table>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Run As</title>

<para>
@@ -1573,9 +1573,9 @@
<literal>RunAsOperation</literal>.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Extending the Identity component</title>

<para>
@@ -1621,6 +1621,6 @@
}
}]]></programlisting>

- </sect1>
+ </section>

</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -163,12 +163,12 @@
</listitem>
<listitem>
<para>
- A Seam component must have a <emphasis>component name</emphasis> specified by the <xref linkend="name-annotation" /> <literal>@Name</literal> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a currently undefined (null) context variable whose name matches that of a Seam component, Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>.
+ A Seam component must have a <emphasis>component name</emphasis> specified by the <xref linkend="name-annotation" /> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a currently undefined (null) context variable whose name matches that of a Seam component, Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>.
</para>
</listitem>
<listitem>
<para>
- Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <xref linkend="scope-annotation" /> <literal>@Scope</literal> annotation. The <literal>User</literal> bean is a session scoped component.
+ Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <xref linkend="scope-annotation" /> annotation. The <literal>User</literal> bean is a session scoped component.
</para>
</listitem>
<listitem>
@@ -271,7 +271,7 @@
</listitem>
<listitem>
<para>
- The <xref linkend="in-annotation" /> <literal>@In</literal> annotation marks an attribute of the bean as injected by Seam. In this case, the attribute is injected from a context variable named <literal>user</literal> (the instance variable name).
+ The <xref linkend="in-annotation" /> annotation marks an attribute of the bean as injected by Seam. In this case, the attribute is injected from a context variable named <literal>user</literal> (the instance variable name).
</para>
</listitem>
<listitem>
@@ -1059,48 +1059,60 @@
JavaBeans (There was no reason to use session beans, since they do not access the database, or have any
other transactional behavior). Let's start with the process definition: </para>

- <example>
- <title></title>
- <programlisting>
-<process-definition name="todo">
+ <formalpara><title>todo.jpdl.xml Example</title>
+ <para>
+ 
+<programlisting><![CDATA[<process-definition name="todo">
+
+ <start-state name="start">
+ <transition to="todo"/>
+ </start-state>
+
+ <task-node name="todo">
+ <task name="todo" description="#{todoList.description}">
+ <assignment actor-id="#{actor.id}"/>
+ </task>
+ <transition to="done"/>
+ </task-node>
+
+ <end-state name="done"/>

-<start-state name="start">
-<transition to="todo"/>
-</start-state>
-
-<task-node name="todo">
-<task name="todo" description="#{todoList.description}">
-<assignment actor-id="#{actor.id}"/>
-</task>
-<transition to="done"/>
-</task-node>
-
-<end-state name="done"/>
-
-</process-definition></programlisting>
-
- <para> The <literal><start-state></literal> node represents the logical start
- of the process. When the process starts, it immediately transitions to the
- <literal>todo</literal> node. </para>
-
- <para> The <literal><task-node></literal> node represents a <emphasis>wait
- state</emphasis>, where business process execution pauses, waiting for one or more
- tasks to be performed. </para>
-
- <para> The <literal><task></literal> element defines a task to be performed by
- a user. Since there is only one task defined on this node, when it is complete,
- execution resumes, and we transition to the end state. The task gets its description
- from a Seam component named <literal>todoList</literal> (one of the JavaBeans). </para>
-
- <para> Tasks need to be assigned to a user or group of users when they are created. In this
- case, the task is assigned to the current user, which we get from a built-in Seam
- component named <literal>actor</literal>. Any Seam component may be used to perform task
- assignment. </para>
-
- <para> The <literal><end-state></literal> node defines the logical end of the
- business process. When execution reaches this node, the process instance is destroyed.
- </para>
- </example>
+</process-definition>]]>
+</programlisting>
+ </para>
+ </formalpara>
+ <formalpara><title>messages.jsp Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<start-state>]]></literal> node represents the logical beginning of the process. When the process begins, it immediately transitions to the <literal>todo</literal> node.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<task-node>]]></literal> node represents a <emphasis>wait state</emphasis>, where business process execution pauses, waiting for one or more tasks to be performed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<task>]]></literal> element defines a task to be performed by a user. Since there is only one task defined on this node, when it is complete, execution resumes, and we transition to the end state. The task receives its description from the <literal>todoList</literal> JavaBean.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tasks are assigned to a user or group of users when they are created. Here, the task is assigned to the current user, retrieved from the built-in <literal>actor</literal> Seam component. (Any Seam component may be used to perform task assignment.)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<end-state>]]></literal> node defines the logical end of the business process. When execution reaches this node, the process instance is destroyed.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>
+

<para> If we view this process definition using the process definition editor provided by JBossIDE, this is
@@ -1180,41 +1192,53 @@
<para> The second JavaBean is responsible for starting business process instances, and ending tasks. </para>


- <example>
- <title></title>
- <programlisting>
-@Name("todoList")
+ <formalpara><title>TodoList.java Example</title>
+ <para>
+<programlisting><![CDATA[@Name("todoList")
public class TodoList {
-
- private String description;
-
- public String getDescription()
- {
- return description;
- }
+ private String description;
+
+ public String getDescription() {
+ return description;
+ }

- public void setDescription(String description) {
- this.description = description;
- }
-
- @CreateProcess(definition="todo")
- public void createTodo() {}
-
- @StartTask @EndTask
- public void done() {}
+ public void setDescription(String description) {
+ this.description = description;
+ }
+
+ @CreateProcess(definition="todo")
+ public void createTodo() {}
+
+ @StartTask @EndTask
+ public void done() {}

-}</programlisting>
-
- <para> The description property accepts user input form the JSP page, and exposes it to the
- process definition, allowing the task description to be set. </para>
-
- <para> The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM process
- instance for the named process definition. </para>
-
- <para> The Seam <literal>@StartTask</literal> annotation starts work on a task. The
- <literal>@EndTask</literal> ends the task, and allows the business process execution
- to resume. </para>
- </example>
+}]]>
+</programlisting>
+ </para>
+ </formalpara>
+ 
+ <formalpara><title>TodoList.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The description property accepts user input from the JSP page, and exposes it to the process definition, allowing the task description to be set.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM process instance for the named process definition.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Seam <literal>@StartTask</literal> annotation starts work on a task. The <literal>@EndTask</literal> ends the task, and allows the business process execution to resume.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>
+

<para> In a more realistic example, <literal>@StartTask</literal> and <literal>@EndTask</literal> would not
@@ -1379,10 +1403,10 @@
configuration and not very interesting. </para>
</section>

- <section>
+

</section>

@@ -1412,70 +1436,89 @@
<para> The example is implemented using one JavaBean, three JSP pages and a jPDL pageflow definition. Let's
begin with the pageflow: </para>

- <example>
- <title></title>
- <programlisting>
-<pageflow-definition
+ <formalpara><title>pageflow.jpdl.xml Example</title>
+ <para>
+<programlisting><![CDATA[<pageflow-definition
xmlns="http://jboss.com/products/seam/pageflow"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://jboss.com/products/seam/pageflow
- http://jboss.com/products/seam/pageflow-2.1.xsd"
- name="numberGuess">
+ xsi:schemaLocation=
+ "http://jboss.com/products/seam/pageflow
+ http://jboss.com/products/seam/pageflow-2.2.xsd"
+ name="numberGuess">

-<start-page name="displayGuess" view-id="/numberGuess.jspx">
- <redirect/>
- <transition name="guess" to="evaluateGuess">
- <action expression="#{numberGuess.guess}"/>
- </transition>
- <transition name="giveup" to="giveup"/>
- </start-page>
+ <start-page name="displayGuess" view-id="/numberGuess.jspx">
+ <redirect/>
+ <transition name="guess" to="evaluateGuess">
+ <action expression="#{numberGuess.guess}"/>
+ </transition>
+ <transition name="giveup" to="giveup"/>
+ <transition name="cheat" to="cheat"/>
+ </start-page>

- <decision name="evaluateGuess" expression="#{numberGuess.correctGuess}">
- <transition name="true" to="win"/>
- <transition name="false" to="evaluateRemainingGuesses"/>
- </decision>
+ <decision name="evaluateGuess" expression="#{numberGuess.correctGuess}">
+ <transition name="true" to="win"/>
+ <transition name="false" to="evaluateRemainingGuesses"/>
+ </decision>

- <decision name="evaluateRemainingGuesses" expression="#{numberGuess.lastGuess}">
- <transition name="true" to="lose"/>
- <transition name="false" to="displayGuess"/>
- </decision>
+ <decision name="evaluateRemainingGuesses"
+ expression="#{numberGuess.lastGuess}">
+ <transition name="true" to="lose"/>
+ <transition name="false" to="displayGuess"/>
+ </decision>

- <page name="giveup" view-id="/giveup.jspx">
- <redirect/>
- <transition name="yes" to="lose"/>
- <transition name="no" to="displayGuess"/>
- </page>
+ <page name="giveup" view-id="/giveup.jspx">
+ <redirect/>
+ <transition name="yes" to="lose"/>
+ <transition name="no" to="displayGuess"/>
+ </page>

- <page name="win" view-id="/win.jspx">
- <redirect/>
- <end-conversation/>
- </page>
+ <process-state name="cheat">
+ <sub-process name="cheat"/>
+ <transition to="displayGuess"/>
+ </process-state>

- <page name="lose" view-id="/lose.jspx">
- <redirect/>
- <end-conversation/>
- </page>
+ <page name="win" view-id="/win.jspx">
+ <redirect/>
+ <end-conversation/>
+ </page>

-</pageflow-definition></programlisting>
-
- <para> The <literal><page></literal> element defines a wait state where the
- system displays a particular JSF view and waits for user input. The
- <literal>view-id</literal> is the same JSF view id used in plain JSF navigation rules.
- The <literal>redirect</literal> attribute tells Seam to use post-then-redirect when
- navigating to the page. (This results in friendly browser URLs.) </para>
-
- <para> The <literal><transition></literal> element names a JSF outcome. The
- transition is triggered when a JSF action results in that outcome. Execution will then
- proceed to the next node of the pageflow graph, after invocation of any jBPM transition
- actions. </para>
-
- <para> A transition <literal><action></literal> is just like a JSF action,
- except that it occurs when a jBPM transition occurs. The transition action can invoke
- any Seam component. </para>
-
- <para> A <literal><decision></literal> node branches the pageflow, and
- determines the next node to execute by evaluating a JSF EL expression. </para>
- </example>
+ <page name="lose" view-id="/lose.jspx">
+ <redirect/>
+ <end-conversation/>
+ </page>
+
+</pageflow-definition>]]>
+</programlisting>
+ </para>
+ </formalpara>
+ 
+ <formalpara><title>pageflow.jpdl.xml Explanatory Notes.</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<page>]]></literal> element defines a wait state, during which the system displays a particular JSF view and waits for user input. The <literal>view-id</literal> is the same JSF view ID used in plain JSF navigation rules. The <literal>redirect</literal> attribute tells Seam to use post-then-redirect when navigating to the page. (This results in browser-friendly URLs.)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal><![CDATA[<transition>]]></literal> element names a JSF outcome. The transition itself is triggered when a JSF action results in the named outcome. After any jBPM transition actions are invoked, execution will proceed to the next node of the pageflow graph.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A transition <literal><![CDATA[<action>]]></literal> is just like a JSF action, except that it is triggered when a jBPM transition occurs. The transition action can invoke any Seam component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A <literal><![CDATA[<decision>]]></literal> node branches the pageflow, and determines the next node to be executed by evaluating a JSF EL expression.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>
+

<para> Here is what the pageflow looks like in the JBoss Developer Studio pageflow editor: </para>
@@ -1608,124 +1651,115 @@
<para> As is <literal>lose.jspx</literal> (which I can't be bothered copy/pasting). Finally, the JavaBean
Seam component: </para>

- <example>
- <title></title>
- <programlistingco>
- <areaspec>
- <area id="numberguess-create" coords="13"/>
- </areaspec>
- <programlisting>
-@Name("numberGuess")
+ <formalpara><title>NumberGuess.java Example</title>
+ <para>
+<programlisting><![CDATA[@Name("numberGuess")
@Scope(ScopeType.CONVERSATION)
public class NumberGuess implements Serializable {

- private int randomNumber;
- private Integer currentGuess;
- private int biggest;
- private int smallest;
- private int guessCount;
- private int maxGuesses;
- private boolean cheated;
-
- @Create
- public void begin()
- {
- randomNumber = new Random().nextInt(100);
- guessCount = 0;
- biggest = 100;
- smallest = 1;
- }
-
- public void setCurrentGuess(Integer guess)
- {
- this.currentGuess = guess;
- }
-
- public Integer getCurrentGuess()
- {
- return currentGuess;
- }
-
- public void guess()
- {
- if (currentGuess>randomNumber)
- {
- biggest = currentGuess - 1;
- }
- if (currentGuess<randomNumber)
- {
- smallest = currentGuess + 1;
- }
- guessCount ++;
- }
-
- public boolean isCorrectGuess()
- {
- return currentGuess==randomNumber;
- }
-
- public int getBiggest()
- {
- return biggest;
- }
-
- public int getSmallest()
- {
- return smallest;
- }
-
- public int getGuessCount()
- {
- return guessCount;
- }
-
- public boolean isLastGuess()
- {
- return guessCount==maxGuesses;
- }
+ private int randomNumber;
+ private Integer currentGuess;
+ private int biggest;
+ private int smallest;
+ private int guessCount;
+ private int maxGuesses;
+ private boolean cheated;
+
+ @Create
+ public void begin() {
+ randomNumber = new Random().nextInt(100);
+ guessCount = 0;
+ biggest = 100;
+ smallest = 1;
+ }
+
+ public void setCurrentGuess(Integer guess) {
+ this.currentGuess = guess;
+ }
+
+ public Integer getCurrentGuess() {
+ return currentGuess;
+ }
+
+ public void guess() {
+ if (currentGuess>randomNumber) {
+ biggest = currentGuess - 1;
+ }
+ if (currentGuess<randomNumber) {
+ smallest = currentGuess + 1;
+ }
+ guessCount ++;
+ }
+
+ public boolean isCorrectGuess() {
+ return currentGuess==randomNumber;
+ }
+
+ public int getBiggest() {
+ return biggest;
+ }
+
+ public int getSmallest() {
+ return smallest;
+ }
+
+ public int getGuessCount() {
+ return guessCount;
+ }
+
+ public boolean isLastGuess() {
+ return guessCount==maxGuesses;
+ }

- public int getRemainingGuesses() {
- return maxGuesses-guessCount;
- }
+ public int getRemainingGuesses() {
+ return maxGuesses-guessCount;
+ }

- public void setMaxGuesses(int maxGuesses) {
- this.maxGuesses = maxGuesses;
- }
+ public void setMaxGuesses(int maxGuesses) {
+ this.maxGuesses = maxGuesses;
+ }

- public int getMaxGuesses() {
- return maxGuesses;
- }
+ public int getMaxGuesses() {
+ return maxGuesses;
+ }

- public int getRandomNumber() {
- return randomNumber;
- }
+ public int getRandomNumber() {
+ return randomNumber;
+ }

- public void cheated()
- {
- cheated = true;
- }
-
- public boolean isCheat() {
- return cheated;
- }
-
- public List<Integer> getPossibilities()
- {
- List<Integer> result = new ArrayList<Integer>();
- for(int i=smallest; i<=biggest; i++) result.add(i);
- return result;
- }
-
-}</programlisting>
- <calloutlist>
- <callout arearefs="numberguess-create">
- <para> The first time a JSP page asks for a <literal>numberGuess</literal> component, Seam
- will create a new one for it, and the <literal>@Create</literal> method will be invoked,
- allowing the component to initialize itself. </para>
- </callout>
- </calloutlist>
- </programlistingco>
- </example>
+ public void cheated() {
+ cheated = true;
+ }
+
+ public boolean isCheat() {
+ return cheated;
+ }
+
+ public List<Integer> getPossibilities() {
+ List<Integer> result = new ArrayList<Integer>();
+ for(int i=smallest; i<=biggest; i++) result.add(i);
+ return result;
+ }
+
+}]]>
+</programlisting>
+ </para>
+ </formalpara>
+ 
+ <formalpara><title>NumberGuess.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The first time a JSP page asks for a <literal>numberGuess</literal> component, Seam creates a new component, and the <literal>@Create</literal> method will be invoked, allowing the component to initialize itself.
+ </para>
+ </listitem>
+ </orderedlist>
+ 
+ 
+ </para>
+ </formalpara>
+

@@ -1758,10 +1792,10 @@

</section>

- <section>
+

</section>

@@ -1937,208 +1971,216 @@
<para> The search functionality is implemented using a session-scope stateful session bean, similar to the
one we saw in the message list example above. </para>

- <example>
- <title></title>
- 
- <programlisting>
-@Stateful
+ <formalpara><title>HotelSearchingAction.java Example</title>
+ <para>
+
+<programlisting><![CDATA[@Stateful
@Name("hotelSearch")
@Scope(ScopeType.SESSION)
@Restrict("#{identity.loggedIn}")
-public class HotelSearchingAction implements HotelSearching
-{
+public class HotelSearchingAction implements HotelSearching {

- @PersistenceContext
- private EntityManager em;
-
- private String searchString;
- private int pageSize = 10;
- private int page;
-
- @DataModel
- private List<Hotel> hotels;
-
- public void find()
- {
- page = 0;
- queryHotels();
- }
- public void nextPage()
- {
- page++;
- queryHotels();
- }
-
- private void queryHotels()
- {
- hotels =
- em.createQuery("select h from Hotel h where lower(h.name) like #{pattern} " +
- "or lower(h.city) like #{pattern} " +
- "or lower(h.zip) like #{pattern} " +
- "or lower(h.address) like #{pattern}")
+ @PersistenceContext
+ private EntityManager em;
+
+ private String searchString;
+ private int pageSize = 10;
+ private int page;
+
+ @DataModel
+ private List<Hotel> hotels;
+
+ public void find() {
+ page = 0;
+ queryHotels();
+ }
+ public void nextPage() {
+ page++;
+ queryHotels();
+ }
+
+ private void queryHotels() {
+ hotels = em.createQuery(
+ "select h from Hotel h where lower(h.name) like #{pattern}" +
+ "or lower(h.city) like #{pattern} " +
+ "or lower(h.zip) like #{pattern} " +
+ "or lower(h.address) like #{pattern}")
.setMaxResults(pageSize)
.setFirstResult( page * pageSize )
.getResultList();
- }
-
- public boolean isNextPageAvailable()
- {
- return hotels!=null && hotels.size()==pageSize;
- }
-
- public int getPageSize() {
- return pageSize;
- }
-
- public void setPageSize(int pageSize) {
- this.pageSize = pageSize;
- }
-
- @Factory(value="pattern", scope=ScopeType.EVENT)
- public String getSearchPattern()
- {
- return searchString==null ?
- "%" : '%' + searchString.toLowerCase().replace('*', '%') + '%';
- }
-
- public String getSearchString()
- {
- return searchString;
- }
-
- public void setSearchString(String searchString)
- {
- this.searchString = searchString;
- }
-
- @Remove
- public void destroy() {}
-} </programlisting>
-
- <para> The EJB standard <literal>@Stateful</literal> annotation identifies this class as a
- stateful session bean. Stateful session beans are scoped to the conversation context by
- default. </para>
-
- <para> The <literal>@Restrict</literal> annotation applies a security restriction to the
- component. It restricts access to the component allowing only logged-in users. The
- security chapter explains more about security in Seam. </para>
-
- <para> The
- <literal>@DataModel</literal>
- annotation exposes a <literal>List</literal> as a JSF
- <literal>ListDataModel</literal>. This makes it easy to implement clickable lists for
- search screens. In this case, the list of hotels is exposed to the page as a
- <literal>ListDataModel</literal> in the conversation variable named
- <literal>hotels</literal>. </para>
-
- <para> The EJB standard <literal>@Remove</literal> annotation specifies that a stateful
- session bean should be removed and its state destroyed after invocation of the annotated
- method. In Seam, all stateful session beans must define a method with no parameters marked
- <literal>@Remove</literal>. This method will be
- called when Seam destroys the session context.</para>
- </example>
+ }
+
+ public boolean isNextPageAvailable() {
+ return hotels!=null && hotels.size()==pageSize;
+ }
+
+ public int getPageSize() {
+ return pageSize;
+ }
+
+ public void setPageSize(int pageSize) {
+ this.pageSize = pageSize;
+ }
+
+ @Factory(value="pattern", scope=ScopeType.EVENT)
+ public String getSearchPattern() {
+ return searchString==null ?
+ "%" : '%' + searchString.toLowerCase().replace('*', '%') + '%';
+ }
+
+ public String getSearchString() {
+ return searchString;
+ }
+
+ public void setSearchString(String searchString) {
+ this.searchString = searchString;
+ }
+
+ @Remove
+ public void destroy() {}
+}]]>
+</programlisting>
+ </para>
+ </formalpara>
+ <formalpara><title>NumberGuess.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The EJB standard <literal>@Stateful</literal> annotation identifies this class as a stateful session bean. Stateful session beans are scoped to the conversation context by default.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>@Restrict</literal> annotation applies a security restriction to the component. It restricts access to the component, allowing only logged-in users. The security chapter explains more about security in Seam.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <xref linkend="datamodel-annotation" /> annotation exposes a <literal>List</literal> as a JSF <literal>ListDataModel</literal>. This makes it easy to implement clickable lists for search screens. In this case, the list of hotels is exposed to the page as a <literal>ListDataModel</literal> in the conversation variable named <literal>hotels</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The EJB standard <literal>@Remove</literal> annotation specifies that a stateful session bean should be removed and its state destroyed after invocation of the annotated method. In Seam, all stateful session beans must define a method <literal>@Remove</literal>, with no marked parameters. This method will be called when Seam destroys the session context.
+ </para>
+ </listitem>
+ </orderedlist>
+ 
+ 
+ </para>
+ </formalpara>
+

<para> The main page of the application is a Facelets page. Let's look at the fragment which relates to
searching for hotels: </para>
- <example>
- <title></title>
- 
- <programlisting>
-<div class="section">
+ <formalpara><title>main.xhtml Example</title>
+ <para>
+<programlisting><![CDATA[<div class="section">

-<span class="errors">
- <h:messages globalOnly="true"/>
-</span>
+ <span class="errors">
+ <h:messages globalOnly="true"/>
+ </span>

-<h1>Search Hotels</h1>
+ <h1>Search Hotels</h1>

-<h:form id="searchCriteria">
-<fieldset>
- <h:inputText id="searchString" value="#{hotelSearch.searchString}"
- style="width: 165px;">
- <a:support event="onkeyup" actionListener="#{hotelSearch.find}"
- reRender="searchResults" />
- </h:inputText>
-
- <a:commandButton id="findHotels" value="Find Hotels" action="#{hotelSearch.find}"
- reRender="searchResults"/>
-
- <a:status>
- <f:facet name="start">
- <h:graphicImage value="/img/spinner.gif"/>
- </f:facet>
- </a:status>
- <br/>
- <h:outputLabel for="pageSize">Maximum results:</h:outputLabel>
- <h:selectOneMenu value="#{hotelSearch.pageSize}" id="pageSize">
- <f:selectItem itemLabel="5" itemValue="5"/>
- <f:selectItem itemLabel="10" itemValue="10"/>
- <f:selectItem itemLabel="20" itemValue="20"/>
- </h:selectOneMenu>
- </fieldset>
- </h:form>
+ <h:form id="searchCriteria">
+ <fieldset>
+ <h:inputText id="searchString" value="#{hotelSearch.searchString}"
+ style="width: 165px;">
+ <a:support event="onkeyup" actionListener="#{hotelSearch.find}"
+ reRender="searchResults" />
+ </h:inputText>
+
+ <a:commandButton id="findHotels" value="Find Hotels"
+ action="#{hotelSearch.find}"
+ reRender="searchResults"/>
+
+ <a:status>
+ <f:facet name="start">
+ <h:graphicImage value="/img/spinner.gif"/>
+ </f:facet>
+ </a:status>
+ <br/>
+ <h:outputLabel for="pageSize">Maximum results:</h:outputLabel>
+ <h:selectOneMenu value="#{hotelSearch.pageSize}" id="pageSize">
+ <f:selectItem itemLabel="5" itemValue="5"/>
+ <f:selectItem itemLabel="10" itemValue="10"/>
+ <f:selectItem itemLabel="20" itemValue="20"/>
+ </h:selectOneMenu>
+ </fieldset>
+ </h:form>

- </div>
+</div>

- <a:outputPanel id="searchResults">
- <div class="section">
- <h:outputText value="No Hotels Found"
- rendered="#{hotels != null and hotels.rowCount==0}"/>
- <h:dataTable id="hotels" value="#{hotels}" var="hot"
- rendered="#{hotels.rowCount>0}">
- <h:column>
- <f:facet name="header">Name</f:facet>
- #{hot.name}
- </h:column>
- <h:column>
- <f:facet name="header">Address</f:facet>
- #{hot.address}
- </h:column>
- <h:column>
- <f:facet name="header">City, State</f:facet>
- #{hot.city}, #{hot.state}, #{hot.country}
- </h:column>
- <h:column>
- <f:facet name="header">Zip</f:facet>
- #{hot.zip}
- </h:column>
- <h:column>
- <f:facet name="header">Action</f:facet>
- <s:link id="viewHotel" value="View Hotel"
- action="#{hotelBooking.selectHotel(hot)}"/>
- </h:column>
- </h:dataTable>
- <s:link value="More results" action="#{hotelSearch.nextPage}"
- rendered="#{hotelSearch.nextPageAvailable}"/>
- </div>
-</a:outputPanel>
+<a:outputPanel id="searchResults">
+ <div class="section">
+ <h:outputText value="No Hotels Found"
+ rendered="#{hotels != null and hotels.rowCount==0}"/>
+ <h:dataTable id="hotels" value="#{hotels}" var="hot"
+ rendered="#{hotels.rowCount>0}">
+ <h:column>
+ <f:facet name="header">Name</f:facet>
+ #{hot.name}
+ </h:column>
+ <h:column>
+ <f:facet name="header">Address</f:facet>
+ #{hot.address}
+ </h:column>
+ <h:column>
+ <f:facet name="header">City, State</f:facet>
+ #{hot.city}, #{hot.state}, #{hot.country}
+ </h:column>
+ <h:column>
+ <f:facet name="header">Zip</f:facet>
+ #{hot.zip}
+ </h:column>
+ <h:column>
+ <f:facet name="header">Action</f:facet>
+ <s:link id="viewHotel" value="View Hotel"
+ action="#{hotelBooking.selectHotel(hot)}"/>
+ </h:column>
+ </h:dataTable>
+ <s:link value="More results" action="#{hotelSearch.nextPage}"
+ rendered="#{hotelSearch.nextPageAvailable}"/>
+ </div>
+</a:outputPanel>]]>
</programlisting>
-
- <para> The RichFaces Ajax <literal><a:support></literal> tag allows a JSF action
- event listener to be called by asynchronous <literal>XMLHttpRequest</literal> when a
- JavaScript event like <literal>onkeyup</literal> occurs. Even better, the
- <literal>reRender</literal> attribute lets us render a fragment of the JSF page and
- perform a partial page update when the asynchronous response is received. </para>
-
- <para> The RichFaces Ajax <literal><a:status></literal> tag lets us display a cheesy
- annimated image while we wait for asynchronous requests to return. </para>
-
- <para> The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a region of
- the page which can be re-rendered by an asynchronous request. </para>
-
- <para> The Seam <literal><s:link></literal> tag lets us attach a JSF action
- listener to an ordinary (non-JavaScript) HTML link. The advantage of this over the
- standard JSF <literal><h:commandLink></literal> is that it preserves the
- operation of "open in new window" and "open in new tab". Also notice that we use a
- method binding with a parameter: <literal>#{hotelBooking.selectHotel(hot)}</literal>.
- This is not possible in the standard Unified EL, but Seam provides an extension to the
- EL that lets you use parameters on any method binding expression. </para>
- <para> If you're wondering how navigation occurs,
- you can find all the rules in <literal>WEB-INF/pages.xml</literal>;
- this is discussed in the navigation section of this book. </para>
-
- </example>
+ </para>
+ </formalpara>
+ <formalpara><title>main.xhtml Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The RichFaces Ajax <literal><![CDATA[<a:support>]]></literal> tag allows a JSF action event listener to be called by asynchronous <literal>XMLHttpRequest</literal> when a JavaScript event such as <literal>onkeyup</literal> occurs. Even better, the <literal>reRender</literal> attribute lets us render a fragment of the JSF page and perform a partial page update when the asynchronous response is received.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The RichFaces Ajax <literal><![CDATA[<a:status>]]></literal> tag lets us display an animated image while we wait for asynchronous requests to return.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The RichFaces Ajax <literal><![CDATA[<a:outputPanel>]]></literal> tag defines a region of the page which can be re-rendered by an asynchronous request.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Seam <literal><![CDATA[<s:link>]]></literal> tag lets us attach a JSF action listener to an ordinary (non-JavaScript) HTML link. The advantage of this over the standard JSF <literal><![CDATA[<h:commandLink>]]></literal> is that it preserves the "open in new window" and "open in new tab" operations. Also note that we use a method binding with a parameter: <literal>#{hotelBooking.selectHotel(hot)}</literal>. This is not possible in standard Unified EL, but Seam provides an extension to an EL that allows parameters on any method binding expression.
+ </para>
+ <para>
+ Navigation rules can be found in <literal>WEB-INF/pages.xml</literal>. These are discussed further in <xref linkend="events.pageaction.navigation" />.
+ </para>
+ </listitem>
+ </orderedlist>
+ 
+ </para>
+ </formalpara>
+

<para> This page displays the search results dynamically as we type, and lets us choose a hotel and pass it
@@ -2150,126 +2192,125 @@
achieve a natural cache of persistent data related to the conversation. The following code example is
pretty long. But if you think of it as a list of scripted actions that implement the various steps of
the conversation, it's understandable. Read the class from top to bottom, as if it were a story. </para>
- <example>
- <title></title>
- 
- <programlisting>
-@Stateful
+ <formalpara><title>HotelBookingAction.java Example</title>
+ <para>
+<programlisting><![CDATA[@Stateful
@Name("hotelBooking")
@Restrict("#{identity.loggedIn}")
-public class HotelBookingAction implements HotelBooking
-{
+public class HotelBookingAction implements HotelBooking {

- @PersistenceContext(type=EXTENDED)
- private EntityManager em;
-
- @In
- private User user;
-
- @In(required=false) @Out
- private Hotel hotel;
-
- @In(required=false)
- @Out(required=false)
- private Booking booking;
-
- @In
- private FacesMessages facesMessages;
-
- @In
- private Events events;
-
- @Logger
- private Log log;
-
- private boolean bookingValid;
-
- @Begin
- public void selectHotel(Hotel selectedHotel)
- {
- hotel = em.merge(selectedHotel);
- }
-
- public void bookHotel()
- {
- booking = new Booking(hotel, user);
- Calendar calendar = Calendar.getInstance();
- booking.setCheckinDate( calendar.getTime() );
- calendar.add(Calendar.DAY_OF_MONTH, 1);
- booking.setCheckoutDate( calendar.getTime() );
- }
-
- public void setBookingDetails()
- {
- Calendar calendar = Calendar.getInstance();
- calendar.add(Calendar.DAY_OF_MONTH, -1);
- if ( booking.getCheckinDate().before( calendar.getTime() ) )
- {
- facesMessages.addToControl("checkinDate", "Check in date must be a future date");
- bookingValid=false;
- }
- else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )
- {
- facesMessages.addToControl("checkoutDate",
- "Check out date must be later than check in date");
- bookingValid=false;
- }
- else
- {
- bookingValid=true;
- }
- }
-
- public boolean isBookingValid()
- {
- return bookingValid;
- }
-
- @End
- public void confirm()
- {
- em.persist(booking);
- facesMessages.add("Thank you, #{user.name}, your confimation number " +
- " for #{hotel.name} is #{booki g.id}");
- log.info("New booking: #{booking.id} for #{user.username}");
- events.raiseTransactionSuccessEvent("bookingConfirmed");
- }
-
- @End
- public void cancel() {}
-
- @Remove
- public void destroy() {}
+ @PersistenceContext(type=EXTENDED)
+ private EntityManager em;
+
+ @In
+ private User user;
+
+ @In(required=false) @Out
+ private Hotel hotel;
+
+ @In(required=false)
+ @Out(required=false)
+ private Booking booking;
+
+ @In
+ private FacesMessages facesMessages;
+
+ @In
+ private Events events;
+
+ @Logger
+ private Log log;
+
+ private boolean bookingValid;
+
+ @Begin
+ public void selectHotel(Hotel selectedHotel) {
+ hotel = em.merge(selectedHotel);
+ }
+
+ public void bookHotel() {
+ booking = new Booking(hotel, user);
+ Calendar calendar = Calendar.getInstance();
+ booking.setCheckinDate( calendar.getTime() );
+ calendar.add(Calendar.DAY_OF_MONTH, 1);
+ booking.setCheckoutDate( calendar.getTime() );
+ }
+
+ public void setBookingDetails() {
+ Calendar calendar = Calendar.getInstance();
+ calendar.add(Calendar.DAY_OF_MONTH, -1);
+ if ( booking.getCheckinDate().before( calendar.getTime() ) ) {
+ facesMessages.addToControl("checkinDate",
+ "Check in date must be a future date");
+ bookingValid=false;
+ }
+ else if (!booking.getCheckinDate().before(booking.getCheckoutDate()))
+ {
+ facesMessages.addToControl("checkoutDate",
+ "Check out date must be later than check in date");
+ bookingValid=false;
+ }
+ else
+ {
+ bookingValid=true;
+ }
+ }
+
+ public boolean isBookingValid() {
+ return bookingValid;
+ }
+
+ @End
+ public void confirm() {
+ em.persist(booking);
+ facesMessages.add("Thank you, #{user.name}, " +
+ "your confimation number " +
+ "for #{hotel.name} is #{booki g.id}");
+ log.info("New booking: #{booking.id} for #{user.username}");
+ events.raiseTransactionSuccessEvent("bookingConfirmed");
+ }
+
+ @End
+ public void cancel() {}
+
+ @Remove
+ public void destroy() {}]]>
</programlisting>
-
- <para> This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so that any
- entity instances remain managed for the whole lifecycle of the stateful session bean.
- </para>
-
- <para> The
- <literal>@Out</literal>
- annotation declares that an attribute value is <emphasis>outjected</emphasis> to
- a context variable after method invocations. In this case, the context variable named
- <literal>hotel</literal> will be set to the value of the <literal>hotel</literal>
- instance variable after every action listener invocation completes. </para>
-
- <para> The
- <literal>@Begin</literal>
- annotation specifies that the annotated method begins a <emphasis>long-running
- conversation</emphasis>, so the current conversation context will not be destroyed
- at the end of the request. Instead, it will be reassociated with every request from the
- current window, and destroyed either by timeout due to conversation inactivity or
- invocation of a matching <literal>@End</literal> method. </para>
-
- <para> The
- <literal>@End</literal>
- annotation specifies that the annotated method ends the current long-running
- conversation, so the current conversation context will be destroyed at the end of the
- request. </para>
-
- <para> This EJB remove method will be called when Seam destroys the conversation context.
- Don't forget to define this method! </para>
- </example>
+ </para>
+ </formalpara>
+ <formalpara><title>HotelBookingAction.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so that entity instances remain managed for the whole lifecycle of the stateful session bean.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <xref linkend="out-annotation" /> annotation declares that an attribute value is "outjected" to a context variable after method invocations. In this case, the context variable named <literal>hotel</literal> will be set to the value of the <literal>hotel</literal> instance variable after every action listener invocation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>@Begin</literal> annotation specifies that the annotated method begins a <emphasis>long-running conversation</emphasis>, so the current conversation context will not be destroyed at the end of the request. Instead, it will be reassociated with every request from the current window, and destroyed either by timeout due to conversation inactivity or invocation of a matching <literal>@End</literal> method.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <xref linkend="end-annotation" /> annotation specifies that the annotated method ends the current long-running conversation, so the current conversation context will be destroyed at the end of the request.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ This EJB remove method must be defined, and will be called when Seam destroys the conversation context.
+ </para>
+ </listitem>
+ </orderedlist>
+ 
+ </para>
+ </formalpara>
+

<para>
@@ -2377,8 +2418,8 @@
</mediaobject>
</screenshot>

- <para>TODO</para>
- <para>Look in the <literal>dvdstore</literal> directory.</para>
+
</section>

<section id="hibernate">
@@ -2387,8 +2428,8 @@
<para> The Hibernate Booking demo is a straight port of the Booking demo to an alternative architecture that
uses Hibernate for persistence and JavaBeans instead of session beans. </para>

- <para>TODO</para>
- <para>Look in the <literal>hibernate</literal> directory.</para>
+ 
</section>

<section id="blog">

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Webservices.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -7,7 +7,7 @@
services to run within a Seam environment.
</para>

- <sect1>
+ <section>
<title>Configuration and Packaging</title>
<para>
To allow Seam to intercept web service requests so that the necessary Seam contexts can be created for the request,
@@ -40,9 +40,9 @@
</endpoint-config>
</jaxws-config>]]></programlisting>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Conversational Web Services</title>
<para>
So how are conversations propagated between web service requests? Seam uses a SOAP header element present
@@ -89,7 +89,7 @@
As you can see, the response message contains the same <literal>conversationId</literal> element as the request.
</para>

- <sect2>
+ <section>
<title>A Recommended Strategy</title>

<para>
@@ -112,11 +112,11 @@
features to be used in the web service class itself.
</para>

- </sect2>
+ </section>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>An example web service</title>

<para>
@@ -196,7 +196,7 @@
and delegating the real work to a conversational Seam component.
</para>

- </sect1>
+ </section>

</chapter>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml 2009-11-24 00:33:31 UTC (rev 11654)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Xml.xml 2009-11-24 02:12:51 UTC (rev 11655)
@@ -11,7 +11,7 @@
properties file or in <literal>web.xml</literal>, and configuration via <literal>components.xml</literal>.
</para>

- <sect1>
+ <section>
<title>Configuring components via property settings</title>
<para>
Seam components may be provided with configuration properties either via servlet context parameters,
@@ -32,9 +32,9 @@
component named <literal>org.jboss.seam.core.manager</literal> with a setter method named
<literal>setConversationTimeout()</literal>.)
</para>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configuring components via <literal>components.xml</literal></title>

<para>
@@ -241,9 +241,9 @@
(at development time). You'll see this approach used in the Seam examples.
</para>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Fine-grained configuration files</title>
<para>
If you have a large number of components that need to be configured in XML, it makes much more sense
@@ -282,9 +282,9 @@
Alternatively, you may put configuration for all classes in the <literal>com.helloworld</literal>
package in <literal>com/helloworld/components.xml</literal>.
</para>
- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Configurable property types</title>
<para>
Properties of string, primitive or primitive wrapper type may be configured just as you would expect:
@@ -347,9 +347,9 @@
<property name="ruleBase">#{policyPricingRules}</property>
</component>]]></programlisting>

- </sect1>
+ </section>

- <sect1>
+ <section>
<title>Using XML Namespaces</title>
<para>
Throughout the examples, there have been two competing ways of declaring components: with and without
@@ -536,7 +536,7 @@

</itemizedlist>

- </sect1>
+ </section>

</chapter>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11654 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T16:33:32Z

Author: laubai
Date: 2009-11-23 19:33:31 -0500 (Mon, 23 Nov 2009)
New Revision: 11654

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Cache.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
Removed callout syntax, as it breaks in publican.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Cache.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Cache.xml 2009-11-24 00:07:11 UTC (rev 11653)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Cache.xml 2009-11-24 00:33:31 UTC (rev 11654)
@@ -14,7 +14,7 @@
nodes of the cluster. What these silly people are really thinking of
is a "share nothing except for the database" architecture. Of course,
sharing the database is the primary problem with scaling a multi-user
- application—so the claim that this architecture is highly scalable
+ application — so the claim that this architecture is highly scalable
is absurd, and tells you a lot about the kind of applications that these
folks spend most of their time working on.
</para>
@@ -66,7 +66,7 @@
persistence context associated with a conversation-scoped stateful
session bean) acts as a cache of data that has been read in the
current conversation. This cache tends to have a pretty high
- hitrate! Seam optimizes the replication of Seam-managed persistence
+ hit rate! Seam optimizes the replication of Seam-managed persistence
contexts in a clustered environment, and there is no requirement for
transactional consistency with the database (optimistic locking is
sufficient) so you don't need to worry too much about the performance

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 00:07:11 UTC (rev 11653)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Tutorial.xml 2009-11-24 00:33:31 UTC (rev 11654)
@@ -99,105 +99,107 @@
<emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra
annotations that define the class as a Seam component. </para>

- <example>
- <title></title>
- <programlisting role="JAVA">
-@Entity <co id="registration-entity-annotation"/>
+ <formalpara><title>User.java Example</title>
+ <para>
+<programlisting role="JAVA"><![CDATA[@Entity
@Name("user")
@Scope(SESSION)
@Table(name="users")
-public class User implements Serializable
-{
- private static final long serialVersionUID = 1881413500711441951L;
-
- private String username;
- private String password;
- private String name;
-
- public User(String name, String password, String username)
- {
- this.name = name;
- this.password = password;
- this.username = username;
- }
-
- public User() {}
-
- @NotNull @Length(min=5, max=15)
- public String getPassword()
- {
- return password;
- }
+public class User implements Serializable {
+ private static final long serialVersionUID = 1881413500711441951L;
+
+ private String username;
+ private String password;
+ private String name;
+
+ public User(String name, String password, String username) {
+ this.name = name;
+ this.password = password;
+ this.username = username;
+ }
+
+ public User() {}
+
+ @NotNull @Length(min=5, max=15)
+ public String getPassword() {
+ return password;
+ }

- public void setPassword(String password)
- {
- this.password = password;
- }
-
- @NotNull
- public String getName()
- {
- return name;
- }
+ public void setPassword(String password) {
+ this.password = password;
+ }
+
+ @NotNull
+ public String getName() {
+ return name;
+ }

- public void setName(String name)
- {
- this.name = name;
- }
-
- @Id @NotNull @Length(min=5, max=15)
- public String getUsername()
- {
- return username;
- }
+ public void setName(String name) {
+ this.name = name;
+ }
+
+ @Id @NotNull @Length(min=5, max=15)
+ public String getUsername() {
+ return username;
+ }

- public void setUsername(String username)
- {
- this.username = username;
- }
+ public void setUsername(String username) {
+ this.username = username;
+ }

-}</programlisting>
-
- <para> The EJB3 standard <literal>@Entity</literal> annotation indicates that the
- <literal>User</literal> class is an entity bean. </para>
+}]]>
+</programlisting>
+ </para>
+ </formalpara>

- <para> A Seam component needs a <emphasis>component name</emphasis> specified by the
- <literal>@Name</literal>
- annotation. This name must be unique within the Seam application. When JSF
- asks Seam to resolve a context variable with a name that is the same as a Seam
- component name, and the context variable is currently undefined (null), Seam will
- instantiate that component, and bind the new instance to the context variable. In
- this case, Seam will instantiate a <literal>User</literal> the first time JSF
- encounters a variable named <literal>user</literal>. </para>
+<formalpara><title>User.java Explanatory Notes</title>
+<para>

- <para> Whenever Seam instantiates a component, it binds the new instance to a context
- variable in the component's <emphasis>default context</emphasis>. The default
- context is specified using the
- <literal>@Scope</literal>
- annotation. The <literal>User</literal> bean is a session scoped component.
- </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The EJB3 standard <literal>@Entity</literal> annotation indicates that the <literal>User</literal> class is an entity bean.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ A Seam component must have a <emphasis>component name</emphasis> specified by the <xref linkend="name-annotation" /> <literal>@Name</literal> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a currently undefined (null) context variable whose name matches that of a Seam component, Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <xref linkend="scope-annotation" /> <literal>@Scope</literal> annotation. The <literal>User</literal> bean is a session scoped component.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The EJB standard <literal>@Table</literal> annotation indicates that the <literal>User</literal> class is mapped to the <literal>users</literal> table.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>name</literal>, <literal>password</literal>, and <literal>username</literal> are the persistent attributes of the entity bean. All of our persistent attributes define accessor methods. These are needed when this component is used by JSF in the render response and update model values phases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ An empty constructor is required by both the EJB specification and by Seam.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>@NotNull</literal> and <literal>@Length</literal> annotations are part of the Hibernate Validator framework. Seam integrates Hibernate Validator and lets you use it for data validation (even if you are not using Hibernate for persistence).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The EJB standard <literal>@Id</literal> annotation indicates the primary key attribute of the entity bean.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+</formalpara>

- <para> The EJB standard <literal>@Table</literal> annotation indicates that the
- <literal>User</literal> class is mapped to the <literal>users</literal> table.
- </para>
-
- <para>
- <literal>name</literal>, <literal>password</literal> and <literal>username</literal>
- are the persistent attributes of the entity bean. All of our persistent attributes
- define accessor methods. These are needed when this component is used by JSF in the
- render response and update model values phases. </para>
-
- <para> An empty constructor is both required by both the EJB specification and by Seam.
- </para>
-
- <para> The <literal>@NotNull</literal> and <literal>@Length</literal> annotations are
- part of the Hibernate Validator framework. Seam integrates Hibernate Validator and
- lets you use it for data validation (even if you are not using Hibernate for
- persistence). </para>
-
- <para> The EJB standard <literal>@Id</literal> annotation indicates the primary key
- attribute of the entity bean. </para>
- </example>
<para> The most important things to notice in this example are the <literal>@Name</literal> and
<literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component. </para>
<para> We'll see below that the properties of our <literal>User</literal> class are bound
@@ -221,92 +223,136 @@

<para> This is the only really interesting code in the example! </para>

- <example>
- <title></title>
-
- <programlisting>
-@Stateless
+
+
+<formalpara><title>RegisterAction.java Example</title>
+ <para>
+
+
+<programlisting><![CDATA[@Stateless
@Name("register")
-public class RegisterAction implements Register
-{
+public class RegisterAction implements Register {
+ @In
+ private User user;
+
+ @PersistenceContext
+ private EntityManager em;
+
+ @Logger
+ private Log log;
+
+ public String register() {
+ List existing = em.createQuery(
+ "select username from User where username = #{user.username}")
+ .getResultList();
+
+ if (existing.size()==0) {
+ em.persist(user);
+ log.info("Registered new user #{user.username}");
+ return "/registered.xhtml";
+ } else {
+ FacesMessages.instance().add("User #{user.username} already exists");
+ return null;
+ }
+ }

- @In
- private User user;
-
- @PersistenceContext
- private EntityManager em;
-
- @Logger
- private Log log;
-
- public String register()
- {
- List existing = em.createQuery(
- "select username from User where username=#{user.username}")
- .getResultList();
-
- if (existing.size()==0)
- {
- em.persist(user);
- log.info("Registered new user #{user.username}");
- return "/registered.xhtml";
- }
- else
- {
- FacesMessages.instance().add("User #{user.username} already exists");
- return null;
- }
- }
-
-}</programlisting>
-
-
- <para> The EJB standard <literal>@Stateless</literal> annotation marks this class as
- a stateless session bean. </para>
-
- <para> The
- <literal>@In</literal>
- annotation marks an attribute of the bean as injected by Seam. In this case,
- the attribute is injected from a context variable named <literal>user</literal> (the
- instance variable name). </para>
-
- <para> The EJB standard <literal>@PersistenceContext</literal> annotation is used to
- inject the EJB3 entity manager. </para>
-
- <para> The Seam <literal>@Logger</literal> annotation is used to inject the component's
- <literal>Log</literal> instance. </para>
-
- <para> The action listener method uses the standard EJB3
- <literal>EntityManager</literal> API to interact with the database, and returns the
- JSF outcome. Note that, since this is a session bean, a transaction is automatically
- begun when the <literal>register()</literal> method is called, and committed when it
- completes. </para>
-
- <para> Notice that Seam lets you use a JSF EL expression inside EJB-QL. Under the
- covers, this results in an ordinary JPA <literal>setParameter()</literal> call on
- the standard JPA <literal>Query</literal> object. Nice, huh? </para>
-
- <para> The <literal>Log</literal> API lets us easily display templated log messages.
+}]]>
+</programlisting>
+ </para>
+ </formalpara>
+ 
+ <formalpara><title>RegisterAction.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The EJB <literal>@Stateless</literal> annotation marks this class as a stateless session bean.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <xref linkend="in-annotation" /> <literal>@In</literal> annotation marks an attribute of the bean as injected by Seam. In this case, the attribute is injected from a context variable named <literal>user</literal> (the instance variable name).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The EJB standard <literal>@PersistenceContext</literal> annotation is used to inject the EJB3 entity manager.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Seam <literal>@Logger</literal> annotation is used to inject the component's <literal>Log</literal> instance.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The action listener method uses the standard EJB3 <literal>EntityManager</literal> API to interact with the database, and returns the JSF outcome. Note that, since this is a session bean, a transaction begins automatically when the <literal>register()</literal> method is called, and is committed when it completes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Notice that Seam lets you use a JSF EL expression inside EJB-QL. This results in an ordinary JPA <literal>setParameter()</literal> call on the standard JPA <literal>Query</literal> object.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>Log</literal> API allows easily display templated log messages that can include JSF EL expressions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ JSF action listener methods return a string-valued outcome that determines the next page displayed. A null outcome (or a void action listener method) redisplays the previous page. In plain JSF, it is normal to always use a JSF <emphasis>navigation rule</emphasis> to determine the JSF view ID from the outcome. For complex applications, this redirection is good practice. However, for very simple examples like this one, Seam lets you use the JSF view ID as the outcome, eliminating the need for a navigation rule.
+ </para>
+ <note>
+ <para>
+ When a view ID is used as an outcome, Seam always performs a browser redirect.
</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>
+ Seam provides a number of <emphasis>built-in components</emphasis> to help solve common problems. The <literal>FacesMessages</literal> component makes it easy to display templated error or success messages. (As of Seam 2.1, you can use <literal>StatusMessages</literal> instead, to remove the semantic dependency on JSF.) Built-in Seam components may be obtained by injection, or by calling the <literal>instance()</literal> method on the class of the built-in component.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>
+ 
+ <para>
+ Note that we did not explicitly specify a <literal>@Scope</literal> this time. Each Seam component type has a default scope, which will be used if scope is not explicitly specified. For stateless session beans, the default scope is the stateless context.
+ </para>
+ <para>
+ The session bean action listener performs the business and persistence logic for our mini-application. In a more complex application, a separate service layer might be necessary, but Seam allows you to implement your own strategies for application layering. You can make any application as simple, or as complex, as you want.
+ </para>
+ <note>
+ <para>
+ This application is more complex than necessary for the sake of clear example code. All of the application code could have been eliminated by using Seam's application framework controllers.
+ </para>
+ </note>
+ </section>
+
+ <section>
+ <title>The session bean local interface: <literal>Register.java</literal></title>
+ <para>
+ The session bean requires a local interface.
+ </para>
+ <formalpara><title>Register.java Example</title>
+ <para>
+ 
+
+<programlisting role="JAVA"><![CDATA[@Local
+public interface Register {
+ public String register();
+}]]></programlisting>
+ 
+ </para>
+ </formalpara>
+
+
+
+

- <para> JSF action listener methods return a string-valued outcome that determines what
- page will be displayed next. A null outcome (or a void action listener method)
- redisplays the previous page. In plain JSF, it is normal to always use a JSF
- <emphasis>navigation rule</emphasis> to determine the JSF view id from the
- outcome. For complex application this indirection is useful and a good practice.
- However, for very simple examples like this one, Seam lets you use the JSF view id
- as the outcome, eliminating the requirement for a navigation rule. <emphasis>Note
- that when you use a view id as an outcome, Seam always performs a browser
- redirect.</emphasis>
- </para>
-
- <para> Seam provides a number of <emphasis>built-in components</emphasis> to help solve
- common problems. The <literal>FacesMessages</literal> component makes it easy to
- display templated error or success messages. Built-in Seam components may be
- obtained by injection, or by calling an <literal>instance()</literal> method.
- </para>
- </example>
-
<para> Note that we did not explicitly specify a <literal>@Scope</literal> this time. Each Seam
component type has a default scope if not explicitly specified. For stateless session beans, the
default scope is the stateless context. Actually, <emphasis>all</emphasis> stateless session
@@ -775,89 +821,99 @@
<para> We want to cache the list of messages in memory between server requests, so we will make this a
stateful session bean. </para>

- <example>
- <title></title>
- <programlisting>
-@Stateful
+
+<formalpara><title>MessageManagerBean.java Example</title>
+ <para>
+
+<programlisting><![CDATA[@Stateful
@Scope(SESSION)
@Name("messageManager")
-public class MessageManagerBean implements Serializable, MessageManager
-{
+public class MessageManagerBean implements Serializable, MessageManager {
+ @DataModel
+ private List<Message> messageList;
+
+ @DataModelSelection
+ @Out(required=false)
+ private Message message;
+
+ @PersistenceContext(type=EXTENDED)
+ private EntityManager em;
+
+ @Factory("messageList")
+ public void findMessages() {
+ messageList = em.createQuery("select msg from Message msg " +
+ "order by msg.datetime desc")
+ .getResultList();
+ }
+
+ public void select() {
+ message.setRead(true);
+ }
+
+ public void delete() {
+ messageList.remove(message);
+ em.remove(message);
+ message=null;
+ }
+
+ @Remove
+ public void destroy() {}

- @DataModel
- private List<Message> messageList;
-
- @DataModelSelection
- @Out(required=false)
- private Message message;
-
- @PersistenceContext(type=EXTENDED)
- private EntityManager em;
-
- @Factory("messageList")
- public void findMessages()
- {
- messageList = em.createQuery("from Message msg order by msg.datetime desc")
- .getResultList();
- }
-
- public void select()
- {
- message.setRead(true);
- }
-
- public void delete()
- {
- messageList.remove(message);
- em.remove(message);
- message=null;
- }
-
- @Remove
- public void destroy() {}
+}]]>
+</programlisting>
+ </para>
+ </formalpara>
+ 
+ <formalpara><title>MessageManagerBean.java Explanatory Notes</title>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The <literal>@DataModel</literal> annotation exposes an attibute of type <literal>java.util.List</literal> to the JSF page as an instance of <literal>javax.faces.model.DataModel</literal>. This allows us to use the list in a JSF <literal><![CDATA[<h:dataTable>]]></literal> with clickable links for each row. In this case, the <literal>DataModel</literal> is made available in a session context variable named <literal>messageList</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>@DataModelSelection</literal> annotation tells Seam to inject the <literal>List</literal> element corresponding to the clicked link.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>@Out</literal> annotation then exposes the selected value directly to the page. Every time a row of the clickable list is selected, the <literal>Message</literal> is injected to the attribute of the stateful bean, and subsequently "outjected" to the event context variable named <literal>message</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>. This means that messages retrieved in the query remain in the managed state for as long as the bean exists. Any subsequent method calls to the stateful bean can therefore update the messages without needing to make an explicit call to the <literal>EntityManager</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The first time we navigate to the JSP page, the <literal>messageList</literal> context variable does not hold a value. The <literal>@Factory</literal> annotation tells Seam to create an instance of <literal>MessageManagerBean</literal> and invoke <literal>findMessages()</literal> — a factory method for messages — to initialize the value.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>select()</literal> action listener method marks the selected <literal>Message</literal> as read, and updates it in the database.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <literal>delete()</literal> action listener method removes the selected <literal>Message</literal> from the database.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All stateful session bean Seam components <emphasis>must</emphasis> have a method <literal>@Remove</literal> defined, with no parameters marked. Seam uses this to remove the stateful bean and clean up any server-side state when the Seam context ends.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>

-}</programlisting>
-
- <para> The <literal>@DataModel</literal> annotation exposes an attibute of type
- <literal>java.util.List</literal> to the JSF page as an instance of
- <literal>javax.faces.model.DataModel</literal>. This allows us to use the list
- in a JSF <literal><h:dataTable></literal> with clickable links for
- each row. In this case, the <literal>DataModel</literal> is made available in a
- session context variable named <literal>messageList</literal>. </para>
-
- <para> The <literal>@DataModelSelection</literal> annotation tells Seam to inject the
- <literal>List</literal> element that corresponded to the clicked link. </para>
-
- <para> The <literal>@Out</literal> annotation then exposes the selected value directly
- to the page. So every time a row of the clickable list is selected, the
- <literal>Message</literal> is injected to the attribute of the stateful bean,
- and the subsequently <emphasis>outjected</emphasis> to the event context variable
- named <literal>message</literal>. </para>
-
- <para> This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>.
- The messages retrieved in the query remain in the managed state as long as the bean
- exists, so any subsequent method calls to the stateful bean can update them without
- needing to make any explicit call to the <literal>EntityManager</literal>. </para>
-
- <para> The first time we navigate to the JSP page, there will be no value in the
- <literal>messageList</literal> context variable. The <literal>@Factory</literal>
- annotation tells Seam to create an instance of <literal>MessageManagerBean</literal>
- and invoke the <literal>findMessages()</literal> method to initialize the value. We
- call <literal>findMessages()</literal> a <emphasis>factory method</emphasis> for
- <literal>messages</literal>. </para>
-
- <para> The <literal>select()</literal> action listener method marks the selected
- <literal>Message</literal> as read, and updates it in the database. </para>
+
+

- <para> The <literal>delete()</literal> action listener method removes the selected
- <literal>Message</literal> from the database. </para>
-
- <para> All stateful session bean Seam components <emphasis>must</emphasis> have a method
- with no parameters marked <literal>@Remove</literal> that Seam uses to remove
- the stateful bean when the Seam context ends, and clean up any server-side state.
- </para>
- </example>
-
<para> Note that this is a session-scoped Seam component. It is associated with the user login session,
and all requests from a login session share the same instance of the component. (In Seam
applications, we usually use session-scoped components sparingly.) </para>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11653 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T16:07:11Z

Author: laubai
Date: 2009-11-23 19:07:11 -0500 (Mon, 23 Nov 2009)
New Revision: 11653

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
Log:
Corrected varlist syntax in Migration chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 00:03:22 UTC (rev 11652)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 00:07:11 UTC (rev 11653)
@@ -1359,17 +1359,25 @@

<variablelist>
<varlistentry>
- <term>Old way:</term>
- <listitem><para>src/model/com/domain/projectname/model/EntityName.java</para></listitem>
- <listitem><para>src/action/com/domain/projectname/model/EntityNameHome.java</para></listitem>
- <listitem><para>src/action/com/domain/projectname/model/EntityNameList.java</para></listitem>
- </varlistentry>
+ <term>Old way:</term>
+ <listitem>
+ <itemizedlist>
+ <listitem><para>src/model/com/domain/projectname/model/EntityName.java</para></listitem>
+ <listitem><para>src/action/com/domain/projectname/model/EntityNameHome.java</para></listitem>
+ <listitem><para>src/action/com/domain/projectname/model/EntityNameList.java</para></listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>

<varlistentry><term>New way:</term>
- <listitem><para>src/model/com/domain/projectname/model/EntityName.java</para></listitem>
- <listitem><para>src/action/com/domain/projectname/action/EntityNameHome.java</para></listitem>
- <listitem><para>src/action/com/domain/projectname/action/EntityNameList.java</para></listitem>
- </varlistentry>
+ <listitem>
+ <itemizedlist>
+ <listitem><para>src/model/com/domain/projectname/model/EntityName.java</para></listitem>
+ <listitem><para>src/action/com/domain/projectname/action/EntityNameHome.java</para></listitem>
+ <listitem><para>src/action/com/domain/projectname/action/EntityNameList.java</para></listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
</variablelist>

@@ -1409,4 +1417,4 @@
</section>
</section>

-</chapter>
+</chapter>
\ No newline at end of file

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11652 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

2009-11-23T16:03:22Z

Author: laubai
Date: 2009-11-23 19:03:22 -0500 (Mon, 23 Nov 2009)
New Revision: 11652

Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Author_Group.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Book_Info.xml
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
Log:
Edited to build in publican.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Author_Group.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Author_Group.xml 2009-11-23 23:37:25 UTC (rev 11651)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Author_Group.xml 2009-11-24 00:03:22 UTC (rev 11652)
@@ -78,4 +78,8 @@
<firstname>Samson</firstname>
<surname>Kittoli</surname>
</editor>
+ <editor>
+ <firstname>Laura</firstname>
+ <surname>Bailey</surname>
+ </editor>
</authorgroup>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Book_Info.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Book_Info.xml 2009-11-23 23:37:25 UTC (rev 11651)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Book_Info.xml 2009-11-24 00:03:22 UTC (rev 11652)
@@ -1,16 +1,16 @@
<?xml version='1.0'?>
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
]>
-<bookinfo id="Seam_Reference_Guide-Seam___Contextual_Components">
- <title>Seam Reference Guide CP03 FP01</title>
- <subtitle>for Use with JBoss Enterprise Application Platform 4.3.0 Cumulative Patch 3 Feature Pack 1</subtitle>
+<bookinfo id="Seam_Reference_Guide_CP07">
+ <title>Seam Reference Guide CP07</title>
+ <subtitle>for Use with JBoss Enterprise Application Platform 4.3.0 Cumulative Patch 7</subtitle>
<edition>2.0</edition>
<pubsnumber>2</pubsnumber>
<productname>JBoss Enterprise Application Platform</productname>
<productnumber>4.3</productnumber>
- <pubdate>December, 2008</pubdate>
+ <pubdate>November, 2009</pubdate>
<isbn>N/A</isbn>
- <abstract><para>This book is a Reference Guide to Seam 2.0.2 for JBoss Enterprise Application Platform 4.3.0_CP03_FP01</para>
+ <abstract><para>This book is a Reference Guide to Seam 2.0.2 for JBoss Enterprise Application Platform 4.3.0_CP07</para>
</abstract>
<corpauthor>
<inlinemediaobject>

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-23 23:37:25 UTC (rev 11651)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml 2009-11-24 00:03:22 UTC (rev 11652)
@@ -424,8 +424,8 @@
</para>

<table>
- <title>Component's in Seam 2</title>
- <tgroup cols="2">
+ <title>Component in Seam 2</title>
+ <tgroup cols="6">
<!-- <colspec colnum="1" colwidth="2*" />
<colspec colnum="2" colwidth="2*" />
<colspec colnum="3" colwidth="2*" />

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11651 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide.

2009-11-23T15:37:25Z

Author: laubai
Date: 2009-11-23 18:37:25 -0500 (Mon, 23 Nov 2009)
New Revision: 11651

Added:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/publican.cfg
Log:
Adding new publican config file.

Added: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/publican.cfg
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/publican.cfg (rev 0)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/publican.cfg 2009-11-23 23:37:25 UTC (rev 11651)
@@ -0,0 +1,7 @@
+# Config::Simple 4.59
+# Tue Nov 24 09:35:12 2009
+
+debug: 1
+xml_lang: en-US
+brand: JBoss
+

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11650 - branches/enterprise/JBPAPP_4_3_FP01/build.

2009-11-23T07:45:01Z

Author: manaRH
Date: 2009-11-23 10:45:01 -0500 (Mon, 23 Nov 2009)
New Revision: 11650

Modified:
branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml
Log:
JBPAPP-3111

Modified: branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml 2009-11-23 13:39:58 UTC (rev 11649)
+++ branches/enterprise/JBPAPP_4_3_FP01/build/root.pom.xml 2009-11-23 15:45:01 UTC (rev 11650)
@@ -814,7 +814,7 @@
<dependency>
<groupId>jfree</groupId>
<artifactId>jfreechart</artifactId>
- <version>1.0.9</version>
+ <version>1.0.13</version>
<exclusions>
<exclusion>
<groupId>junit</groupId>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11649 - in modules/trunk: beans and 3 other directories.

2009-11-23T05:39:58Z

Author: pete.muir@...
Date: 2009-11-23 08:39:58 -0500 (Mon, 23 Nov 2009)
New Revision: 11649

Removed:
modules/trunk/persistence/src/main/java/org/
Modified:
modules/trunk/beans/pom.xml
modules/trunk/persistence/pom.xml
modules/trunk/pom.xml
modules/trunk/version-matrix/pom.xml
Log:
make build work, at least for persistence module, clean up persistence module

Modified: modules/trunk/beans/pom.xml
===================================================================
--- modules/trunk/beans/pom.xml 2009-11-22 18:31:55 UTC (rev 11648)
+++ modules/trunk/beans/pom.xml 2009-11-23 13:39:58 UTC (rev 11649)
@@ -18,14 +18,14 @@
<dependencies>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
+ <groupId>${weld.groupId}</groupId>
<artifactId>jsr299-api</artifactId>
<scope>provided</scope>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-logger</artifactId>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-logger</artifactId>
</dependency>

</dependencies>

Modified: modules/trunk/persistence/pom.xml
===================================================================
--- modules/trunk/persistence/pom.xml 2009-11-22 18:31:55 UTC (rev 11648)
+++ modules/trunk/persistence/pom.xml 2009-11-23 13:39:58 UTC (rev 11649)
@@ -32,20 +32,10 @@
</dependency>

<dependency>
- <groupId>${seam.groupId}</groupId>
- <artifactId>seam-el</artifactId>
- </dependency>
-
- <dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>jsr299-api</artifactId>
+ <groupId>javax.enterprise</groupId>
+ <artifactId>cdi-api</artifactId>
</dependency>

- <dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-logger</artifactId>
- </dependency>
-
</dependencies>

</project>

Modified: modules/trunk/pom.xml
===================================================================
--- modules/trunk/pom.xml 2009-11-22 18:31:55 UTC (rev 11648)
+++ modules/trunk/pom.xml 2009-11-23 13:39:58 UTC (rev 11649)
@@ -90,7 +90,7 @@

<modules>

- <module>version-matrix</module>
+
</modules>

<dependencies>
@@ -124,8 +124,8 @@
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-core-test</artifactId>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-core-test</artifactId>
<scope>test</scope>
</dependency>

@@ -210,7 +210,7 @@
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
<configuration>
- <tagBase>https://svn.jboss.org/repos/webbeans/ri/tags</tagBase>
+ <tagBase>https://svn.jboss.org/repos/weld/ri/tags</tagBase>
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>

Modified: modules/trunk/version-matrix/pom.xml
===================================================================
--- modules/trunk/version-matrix/pom.xml 2009-11-22 18:31:55 UTC (rev 11648)
+++ modules/trunk/version-matrix/pom.xml 2009-11-23 13:39:58 UTC (rev 11649)
@@ -53,8 +53,8 @@
<properties>
<seam.version>3.0.0-SNAPSHOT</seam.version>
<seam.groupId>org.jboss.seam</seam.groupId>
- <webbeans.version>1.0.0-SNAPSHOT</webbeans.version>
- <webbeans.groupId>org.jboss.webbeans</webbeans.groupId>
+ <weld.version>1.0.0</weld.version>
+ <weld.groupId>org.jboss.weld</weld.groupId>
</properties>

<dependencyManagement>
@@ -167,39 +167,39 @@
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>jsr299-api</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>javax.enterprise</groupId>
+ <artifactId>cdi-api</artifactId>
+ <version>1.0</version>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-core</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-core</artifactId>
+ <version>${weld.version}</version>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-core-test</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-core-test</artifactId>
+ <version>${weld.version}</version>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-logger</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-logger</artifactId>
+ <version>${weld.version}</version>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}</groupId>
- <artifactId>webbeans-logging</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>${weld.groupId}</groupId>
+ <artifactId>weld-logging</artifactId>
+ <version>${weld.version}</version>
</dependency>

<dependency>
- <groupId>${webbeans.groupId}.servlet</groupId>
- <artifactId>webbeans-servlet</artifactId>
- <version>${webbeans.version}</version>
+ <groupId>${weld.groupId}.servlet</groupId>
+ <artifactId>weld-servlet</artifactId>
+ <version>${weld.version}</version>
</dependency>

<dependency>
@@ -238,7 +238,7 @@
<dependency>
<groupId>org.jboss.test-harness</groupId>
<artifactId>jboss-test-harness</artifactId>
- <version>1.0.0-SNAPSHOT</version>
+ <version>1.1.0-CR3</version>
</dependency>

<dependency>
@@ -327,7 +327,7 @@

<dependency>
<groupId>${seam.groupId}</groupId>
- <artifactId>seam-webbeans-bridge</artifactId>
+ <artifactId>seam-weld-bridge</artifactId>
<version>${seam.version}</version>
</dependency>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11648 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT.

2009-11-22T10:31:55Z

Author: nico.ben
Date: 2009-11-22 13:31:55 -0500 (Sun, 22 Nov 2009)
New Revision: 11648

Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Security.po
Log:
Italian translation

Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Security.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Security.po 2009-11-22 18:31:22 UTC (rev 11647)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Security.po 2009-11-22 18:31:55 UTC (rev 11648)
@@ -6,7 +6,7 @@
"Project-Id-Version: Security\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-06-25 15:02+0000\n"
-"PO-Revision-Date: 2009-06-25 17:05+0100\n"
+"PO-Revision-Date: 2009-11-22 19:29+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz@...>\n"
"Language-Team: it <stefano.travelli@...>\n"
"MIME-Version: 1.0\n"
@@ -151,7 +151,7 @@
#: Security.xml:113
#, no-c-format
msgid "The simplified authentication method provided by Seam uses a built-in JAAS login module, <literal>SeamLoginModule</literal>, which delegates authentication to one of your own Seam components. This login module is already configured inside Seam as part of a default application policy and as such does not require any additional configuration files. It allows you to write an authentication method using the entity classes that are provided by your own application, or alternatively to authenticate with some other third party provider. Configuring this simplified form of authentication requires the <literal>identity</literal> component to be configured in <literal>components.xml</literal>:"
-msgstr "Il metodo di autenticazione semplificato fornito da Seam usa un modulo di login JAAS già fatto, <literal>SeamLoginModule</literal>, il quale delega l'autenticazione ad uno dei componenti dell'applicazione. Questo modulo di login è già configurato all'interno di Seam come parte dei criteri di gestione di default e in quanto tale non richiede alcun file di configurazione aggiuntivo. Esso consente di scrivere un metodo di autenticazione usando le classi entità che sono fornite dall'applicazione o, in alternativa, di esegure l'autenticazione con qualche altro fornitore di terze parti. Per configurare questa forma semplificata di autentifica è richiesto di di configurare il componente <literal>Identity</literal> in <literal>components.xml</literal>:"
+msgstr "Il metodo di autenticazione semplificato fornito da Seam usa un modulo di login JAAS già fatto, <literal>SeamLoginModule</literal>, il quale delega l'autenticazione ad uno dei componenti dell'applicazione. Questo modulo di login è già configurato all'interno di Seam come parte dei criteri di gestione di default e in quanto tale non richiede alcun file di configurazione aggiuntivo. Esso consente di scrivere un metodo di autenticazione usando le classi entità che sono fornite dall'applicazione o, in alternativa, di esegure l'autenticazione con qualche altro fornitore di terze parti. Per configurare questa forma semplificata di autenticazione è richiesto di configurare il componente <literal>Identity</literal> in <literal>components.xml</literal>:"

#. Tag: programlisting
#: Security.xml:122
@@ -445,7 +445,7 @@
#: Security.xml:301
#, no-c-format
msgid "To summarize: While everyone is doing it, persistent \"Remember Me\" cookies with automatic authentication are a bad practice and should not be used. Cookies that \"remember\" only the users login name, and fill out the login form with that username as a convenience, are not an issue."
-msgstr "In definitiva: benché tutti lo stiano facendo, il cookie \"Ricordami su questo computer\" con l'autenticazione automatica è un cattiva pratica e non dovrebbe essere usata. I cookie che \"ricordano\" solo il nome dell'utente e riempiono la form di accesso con quel nome utente per praticità, non comportano rischi."
+msgstr "In definitiva: benché tutti lo stiano facendo, il cookie \"Ricordami su questo computer\" con l'autenticazione automatica è una cattiva pratica e non dovrebbe essere usata. I cookie che \"ricordano\" solo il nome dell'utente e riempiono la form di accesso con quel nome utente per praticità, non comportano rischi."

#. Tag: para
#: Security.xml:308
@@ -677,7 +677,7 @@
#: Security.xml:396
#, no-c-format
msgid "In the case of a <literal>NotLoggedInException</literal>, it is recommended that the user is redirected to either a login or registration page so that they can log in. For an <literal>AuthorizationException</literal>, it may be useful to redirect the user to an error page. Here's an example of a <literal>pages.xml</literal> file that redirects both of these security exceptions:"
-msgstr "Nel caso della <literal>NotLoggedInException</literal>, si raccomanda che l'utente venga rediretto o sulla pagina di accesso o su quella di registrazione, così che possa accedere. Per una <literal>AuthorizationException</literal>, può essere utile redirigere l'utente su una pagina di errore. Ecco un esempio di un <literal>pages.xml</literal> che redirige entrambe queste eccezioni:"
+msgstr "Nel caso della <literal>NotLoggedInException</literal>, si raccomanda che l'utente venga rediretto o sulla pagina di accesso o su quella di registrazione, così che possa accedere. Per una <literal>AuthorizationException</literal>, può essere utile redirigere l'utente su una pagina di errore. Ecco un esempio di <literal>pages.xml</literal> che redirige entrambe queste eccezioni:"

#. Tag: programlisting
#: Security.xml:403
@@ -725,7 +725,7 @@
#: Security.xml:405
#, no-c-format
msgid "Most web applications require even more sophisticated handling of login redirection, so Seam includes some special functionality for handling this problem."
-msgstr "La maggior parte delle applicazioni web richiede una gestione più sofisticata della redirezione sulla pagina di accesso, perciò Seam include alcune funzionalità speciali per gestire questo problema:"
+msgstr "La maggior parte delle applicazioni web richiede una gestione più sofisticata della redirezione sulla pagina di accesso, perciò Seam include alcune funzionalità speciali per gestire questo problema."

#. Tag: title
#: Security.xml:413
@@ -2098,7 +2098,7 @@
#: Security.xml:1372
#, no-c-format
msgid "If you are using the Identity Management features in your Seam application, then it is not required to provide an authenticator component (see previous Authentication section) to enable authentication. Simply omit the <literal>authenticator-method</literal> from the <literal>identity</literal> configuration in <literal>components.xml</literal>, and the <literal>SeamLoginModule</literal> will by default use <literal>IdentityManager</literal> to authenticate your application's users, without any special configuration required."
-msgstr "Se in un'applicazione Seam si stanno usando le funzioni di gestione delle identità, allora non è richiesto di fornire un componente <literal>authenticator</literal> (vedi il precedente paragrafo Autenticazione) per abilitare l'autenticazione. Basta omettere <literal>authenticator-method</literal> dalla configurazione di <literal>identity</literal> in <literal>components.xml</literal> e il <literal>SeamLoginModule</literal> userà per default <literal>IdentityManager</literal> per autenticare gli utenti dell'applicazione, senza nessuna configurazione speciale."
+msgstr "Se in un'applicazione Seam si stanno usando le funzioni di gestione delle identità, allora non è richiesto di fornire un componente <literal>authenticator</literal> (vedi il precedente paragrafo Autenticazione) per abilitare l'autenticazione. Basta omettere <literal>authenticator-method</literal> dalla configurazione di <literal>identity</literal> in <literal>components.xml</literal> e il <literal>SeamLoginModule</literal> userà di default <literal>IdentityManager</literal> per autenticare gli utenti dell'applicazione, senza nessuna configurazione speciale."

#. Tag: title
#: Security.xml:1383
@@ -2197,7 +2197,7 @@
#: Security.xml:1437
#, no-c-format
msgid "Creates a new user account, with the specified name and password. Returns <literal>true</literal> if successful, or <literal>false</literal> if not."
-msgstr "Crea un nuovo utente con il nome e la password specificate. Restituisce <literal>true</literal> se l'operazione si è conclusa con successo, altrimenti <literal>false</literal>."
+msgstr "Crea un nuovo utente con il nome e la password specificate. Restituisce <literal>true</literal> se l'operazione si è conclusa con successo, oppure <literal>false</literal>."

#. Tag: literal
#: Security.xml:1447
@@ -2661,7 +2661,7 @@
#: Security.xml:2127
#, no-c-format
msgid "The security API produces a number of default faces messages for various security-related events. The following table lists the message keys that can be used to override these messages by specifying them in a <literal>message.properties</literal> resource file. To suppress the message, just put the key with an empty value in the resource file."
-msgstr "Le API di sicurezza producono una serie di messaggi di default per i diversi eventi relaivi alla sicurezza. La seguente tabella elenca le chiavi dei messaggi che possono essere usate per sovrascrivere questi messaggi specificandoli in un file <literal>message.properties</literal>. Per sopprimere un messaggio basta mettere nel file la chiave con un valore vuoto."
+msgstr "Le API di sicurezza producono una serie di messaggi di default per i diversi eventi relativi alla sicurezza. La seguente tabella elenca le chiavi dei messaggi che possono essere usate per sovrascrivere questi messaggi specificandoli in un file <literal>message.properties</literal>. Per sopprimere un messaggio basta mettere nel file la chiave con un valore vuoto."

#. Tag: title
#: Security.xml:2135
@@ -2757,7 +2757,7 @@
#: Security.xml:2233
#, no-c-format
msgid "A role is a <emphasis>group</emphasis>, or <emphasis>type</emphasis>, of user that may have been granted certain privileges for performing one or more specific actions within an application. They are simple constructs, consisting of just a name such as \"admin\", \"user\", \"customer\", etc. They can be granted either to users (or in some cases to other roles), and are used to create logical groups of users for the convenient assignment of specific application privileges."
-msgstr "Un ruolo è un <emphasis>gruppo</emphasis>, o un <emphasis>tipo</emphasis>, di utente al quale possono essere concessi certi privilegi per eseguire una o più azioni specifiche nell'ambito dell'applicazione. Essi sono dei semplici costrutti consistenti solo di un nome che \"amministratore\", \"utente\", \"cliente\", ecc. Possono sia essere concessi ad un utente (o in alcuni casi ad altri ruoli) che essere usati per creare gruppi logici di utenti per facilitare l'assegnazione di determinati privilegi dell'applicazione."
+msgstr "Un ruolo è un <emphasis>gruppo</emphasis>, o un <emphasis>tipo</emphasis>, di utente al quale possono essere concessi certi privilegi per eseguire una o più azioni specifiche nell'ambito dell'applicazione. Essi sono dei semplici costrutti consistenti solo di un nome quale \"amministratore\", \"utente\", \"cliente\", ecc. Possono sia essere concessi ad un utente (o in alcuni casi ad altri ruoli) che essere usati per creare gruppi logici di utenti per facilitare l'assegnazione di determinati privilegi dell'applicazione."

#. Tag: title
#: Security.xml:2251
@@ -2769,7 +2769,7 @@
#: Security.xml:2253
#, no-c-format
msgid "A permission is a privilege (sometimes once-off) for performing a single, specific action. It is entirely possible to build an application using nothing but permissions, however roles offer a higher level of convenience when granting privileges to groups of users. They are slightly more complex in structure than roles, essentially consisting of three \"aspects\"; a target, an action, and a recipient. The target of a permission is the object (or an arbitrary name or class) for which a particular action is allowed to be performed by a specific recipient (or user). For example, the user \"Bob\" may have permission to delete customer objects. In this case, the permission target may be \"customer\", the permission action would be \"delete\" and the recipient would be \"Bob\"."
-msgstr "Un permesso è un privilegio (a volte una-tantum) per eseguire una singola, specifica azione. E' del tutto possibile costruire un'applicazione usando nient'altro che i privilegi, comunque i ruoli offrono un livello di facilitazione più alto quando si tratta di concedere dei privilegi a gruppi di utenti. Essi sono leggermente più complessi nella struttura rispetto ai ruoli ed essenzialmente consistono di tre \"aspetti\": un obiettivo , un'azione e un destinatario. L'obiettivo di un permesso è l'oggetto (o un nome arbitrario o una classe) per il quale è consentito di eseguire una determinata azione da parte di uno specifico destinatario (o utente). Ad esempio, l'utente \"Roberto\" può avere il permesso di cancellare gli oggetti cliente. In questo caso l'obiettivo del permesso può essere \"clienti\", l'azione del permesso sarà \"cancella\" e il recipiente sarà \"Roberto\"."
+msgstr "Un permesso è un privilegio (a volte una-tantum) per eseguire una singola, specifica azione. E' del tutto possibile costruire un'applicazione usando nient'altro che i privilegi, comunque i ruoli offrono un livello di facilitazione più alto quando si tratta di concedere dei privilegi a gruppi di utenti. Essi sono leggermente più complessi nella struttura rispetto ai ruoli ed essenzialmente consistono di tre \"aspetti\": un obiettivo, un'azione e un destinatario. L'obiettivo di un permesso è l'oggetto (o un nome arbitrario o una classe) per il quale è consentito di eseguire una determinata azione da parte di uno specifico destinatario (o utente). Ad esempio, l'utente \"Roberto\" può avere il permesso di cancellare gli oggetti cliente. In questo caso l'obiettivo del permesso può essere \"clienti\", l'azione del permesso sarà \"cancella\" e il destinatario sarà \"Roberto\"."

#. Tag: para
#: Security.xml:2273
@@ -2811,7 +2811,7 @@
#: Security.xml:2302
#, no-c-format
msgid "Seam components may be secured either at the method or the class level, using the <literal>@Restrict</literal> annotation. If both a method and it's declaring class are annotated with <literal>@Restrict</literal>, the method restriction will take precedence (and the class restriction will not apply). If a method invocation fails a security check, then an exception will be thrown as per the contract for <literal>Identity.checkRestriction()</literal> (see Inline Restrictions). A <literal>@Restrict</literal> on just the component class itself is equivalent to adding <literal>@Restrict</literal> to each of its methods."
-msgstr "I componenti Seam possono essere resi sicuri sia a livello di metodo che a livello di classe usando l'annotazione <literal>@Restrict</literal>. Se sia un metodo che la classe in cui è dichiarato sono annotati con <literal>@Restrict</literal>, la restrizione sul metodo ha la precedenza (e la restrizione sulla classe non si applica). Se nell'invocazione di un metodo fallisce il controllo di sicurezza, viene lanciata un'eccezione come definito nel contratto di <literal>Identity.checkRestriction()</literal> (vedi Restrizioni in linea). Una <literal>@Restrict</literal> solo sulla classe del componente stesso è equivalente ad aggiungere <literal>@Restrict</literal> a ciascuno dei suoi metodi."
+msgstr "I componenti Seam possono essere resi sicuri sia a livello di metodo che a livello di classe usando l'annotazione <literal>@Restrict</literal>. Qualora sia un metodo sia la classe in cui questo è dichiarato sono annotati con <literal>@Restrict</literal>, la restrizione sul metodo ha la precedenza (e la restrizione sulla classe non si applica). Se nell'invocazione di un metodo fallisce il controllo di sicurezza, viene lanciata un'eccezione come definito nel contratto di <literal>Identity.checkRestriction()</literal> (vedi Restrizioni in linea). Una <literal>@Restrict</literal> solo sulla classe del componente stesso è equivalente ad aggiungere <literal>@Restrict</literal> a ciascuno dei suoi metodi."

#. Tag: para
#: Security.xml:2312
@@ -2989,7 +2989,7 @@
#: Security.xml:2402
#, no-c-format
msgid "One indication of a well designed user interface is that the user is not presented with options for which they don't have the necessary privileges to use. Seam Security allows conditional rendering of either 1) sections of a page or 2) individual controls, based upon the privileges of the user, using the very same EL expressions that are used for component security."
-msgstr "Uno degli indici di interfaccia utente ben progettata è quando agli utenti non vengono presentate opzioni per le quali essi non hanno i permessi necessari. La sicurezza di Seam consente la visualizzazione condizionale sia di sezioni di una pagina che di singoli controlli, basata sui privilegi dell'utente, usando esattamente le stesse espressioni EL usate nella sicurezza dei componenti."
+msgstr "Uno degli indicatori di interfaccia utente ben progettata è quando agli utenti non vengono presentate opzioni per le quali essi non hanno i permessi necessari. La sicurezza di Seam consente la visualizzazione condizionale sia di sezioni di una pagina che di singoli controlli, basata sui privilegi dell'utente, usando esattamente le stesse espressioni EL usate nella sicurezza dei componenti."

#. Tag: para
#: Security.xml:2409
@@ -3083,7 +3083,7 @@
#: Security.xml:2446
#, no-c-format
msgid "Page security requires that the application is using a <literal>pages.xml</literal> file, however is extremely simple to configure. Simply include a <literal><restrict/></literal> element within the <literal>page</literal> elements that you wish to secure. If no explicit restriction is specified by the <literal>restrict</literal> element, an implied permission of <literal>/viewId.xhtml:render</literal> will be checked when the page is accessed via a non-faces (GET) request, and a permission of <literal>/viewId.xhtml:restore</literal> will be required when any JSF postback (form submission) originates from the page. Otherwise, the specified restriction will be evaluated as a standard security expression. Here's a couple of examples:"
-msgstr "La sicurezza delle pagine richiede che l'applicazione usi un file <literal>pages.xml</literal>. Comunque è molto semplice da configurare. Basta includere un elemento <literal><restrict></literal> all'interno degli elementi <literal>page</literal> che si vogliono rendere sicuri. Se tramite l'elemento <literal>restrict</literal> non viene indicata esplicitamente una restrizione, verrà controllato implicitamente il permesso <literal>/viewId.xhtml:render</literal> quando la richiesta della pagina avviene in modo non-faces (GET), e il permesso<literal>/viewId.xhtml:restore</literal> quando un JSF postback (il submit della form) viene originato dalla pagina. Altrimenti viene la restrizione specificata verrà valutata come una normale espressione di sicurezza. Ecco un paio di esempi:"
+msgstr "La sicurezza delle pagine richiede che l'applicazione usi un file <literal>pages.xml</literal>. Comunque è molto semplice da configurare. Basta includere un elemento <literal><restrict></literal> all'interno degli elementi <literal>page</literal> che si vogliono rendere sicuri. Se tramite l'elemento <literal>restrict</literal> non viene indicata esplicitamente una restrizione, verrà controllato implicitamente il permesso <literal>/viewId.xhtml:render</literal> quando la richiesta della pagina avviene in modo non-faces (GET), e il permesso<literal>/viewId.xhtml:restore</literal> quando un JSF postback (il submit della form) viene originato dalla pagina. Altrimenti la restrizione specificata verrà valutata come una normale espressione di sicurezza. Ecco un paio di esempi:"

#. Tag: programlisting
#: Security.xml:2457
@@ -3197,7 +3197,7 @@
#: Security.xml:2527
#, no-c-format
msgid "Here's an example of how an entity would be configured to perform a security check for any <literal>insert</literal> operations. Please note that the method is not required to do anything, the only important thing in regard to security is how it is annotated:"
-msgstr "Ecco un esempio di come un'entità potrebbe essere configurata per eseguire un controllo di sicurezza per tutte le operazioni <literal>insert</literal>. Notare che non è richiesto che il metodo faccia qualcosa, la sola cosa importante per quanto riguarda la sicurezza è come è annotato:"
+msgstr "Ecco un esempio di come un'entità potrebbe essere configurata per eseguire un controllo di sicurezza per tutte le operazioni <literal>insert</literal>. Notare che non è richiesto che il metodo faccia qualcosa, la sola cosa importante per quanto riguarda la sicurezza è come questo viene annotato:"

#. Tag: programlisting
#: Security.xml:2533
@@ -3379,7 +3379,7 @@
#: Security.xml:2608
#, no-c-format
msgid "Out of the box, Seam comes with annotations for standard CRUD-based permissions, however it is a simple matter to add your own. The following annotations are provided in the <literal>org.jboss.seam.annotations.security</literal> package:"
-msgstr "Così com'è, Seam contiene delle annotazioni per i permessi standard per le operazioni CRUD, comunque è solo questione di aggiungerne altre. Le seguenti annotazioni sono fornire nel pacchetto <literal>org.jboss.seam.annotations.security</literal>:"
+msgstr "Così com'è, Seam contiene delle annotazioni per i permessi standard per le operazioni CRUD, comunque è solo questione di aggiungerne altre. Le seguenti annotazioni sono fornite nel pacchetto <literal>org.jboss.seam.annotations.security</literal>:"

#. Tag: para
#: Security.xml:2615
@@ -3543,7 +3543,7 @@
#: Security.xml:2704
#, no-c-format
msgid "The relevant classes are explained in more detail in the following sections."
-msgstr "Le classi rilevanti sono spiegate in maggiore dettaglio nel seguente paragrafo."
+msgstr "Le classi rilevanti sono spiegate con maggiore dettaglio nel seguente paragrafo."

#. Tag: title
#: Security.xml:2709
@@ -3762,7 +3762,7 @@
#: Security.xml:2947
#, no-c-format
msgid "The configuration for <literal>RuleBasedPermissionResolver</literal> requires that a Drools rule base is first configured in <literal>components.xml</literal>. By default, it expects that the rule base is named <literal>securityRules</literal>, as per the following example:"
-msgstr "La configurazione per <literal>RuleBasedPermissionResolver</literal> richiede che una base di regole venga prima configurata in <literal>components.xml</literal>. Per difetto si aspetta che questa base di regole sia chiamata <literal>securityRules</literal>, come nel seguente esempio:"
+msgstr "La configurazione per <literal>RuleBasedPermissionResolver</literal> richiede che una base di regole venga prima configurata in <literal>components.xml</literal>. Di default questa base di regole viene chiamata <literal>securityRules</literal>, come nel seguente esempio:"

#. Tag: programlisting
#: Security.xml:2953
@@ -3898,7 +3898,7 @@
#: Security.xml:3002
#, no-c-format
msgid "Looking at the body of the rule definition we can notice two distinct sections. Rules have what is known as a left hand side (LHS) and a right hand side (RHS). The LHS consists of the conditional part of the rule, i.e. a list of conditions which must be satisfied for the rule to fire. The LHS is represented by the <literal>when</literal> section. The RHS is the consequence, or action section of the rule that will only be fired if all of the conditions in the LHS are met. The RHS is represented by the <literal>then</literal> section. The end of the rule is denoted by the <literal>end</literal> line."
-msgstr "Guardando il corpo della definizione della regola si possono notare due distinte sezioni. Le regole hanno quello che è noto come lato sinistro (LHS, left hand side) e un lato destro (RHS, right hand side). Il lato sinistro consiste nella parte condizionale della regola, cioè l'elenco delle condizioni che devono essere soddisfatte per la regola si applichi. Il lato sinistro è rappresentato dalla sezione <literal>when</literal>. Il lato destro è la conseguenza, o la parte di azione della regola che si applica solo se tutte le condizioni del lato sinistro sono verificate. Il lato destro è rappresentato dalla sezione <literal>then</literal>. La fine della regola è stabilita dalla linea <literal>end</literal>."
+msgstr "Guardando il corpo della definizione della regola si possono notare due distinte sezioni. Le regole hanno quello che è noto come lato sinistro (LHS, left hand side) e un lato destro (RHS, right hand side). Il lato sinistro consiste nella parte condizionale della regola, cioè l'elenco delle condizioni che devono essere soddisfatte affinché si applichi la regola. Il lato sinistro è rappresentato dalla sezione <literal>when</literal>. Il lato destro è la conseguenza, o la parte di azione della regola che si applica solo se tutte le condizioni del lato sinistro sono verificate. Il lato destro è rappresentato dalla sezione <literal>then</literal>. La fine della regola è stabilita dalla linea <literal>end</literal>."

#. Tag: para
#: Security.xml:3011
@@ -3928,7 +3928,7 @@
#: Security.xml:3035
#, no-c-format
msgid "Besides the <literal>PermissionCheck</literal> facts, there is also a <literal>org.jboss.seam.security.Role</literal> fact for each of the roles that the authenticated user is a member of. These <literal>Role</literal> facts are synchronized with the user's authenticated roles at the beginning of every permission check. As a consequence, any <literal>Role</literal> object that is inserted into the working memory during the course of a permission check will be removed before the next permission check occurs, if the authenticated user is not actually a member of that role. Besides the <literal>PermissionCheck</literal> and <literal>Role</literal> facts, the working memory also contains the <literal>java.security.Principal</literal> object that was created as a result of the authentication process."
-msgstr "Accanto al fatto <literal>PermissionCheck</literal> c'è anche un fatto <literal>org.jboss.seam.security.Role</literal> per ogni ruolo di cui l'utente autenticato è membro. Questi fatti <literal>Role</literal> sono sincronizzati con i ruoli dell'utente autenticato all'inizio di ogni controllo di permesso. Di conseguenza qualsiasi oggetto <literal>Role</literal> che venisse inserito nella working memory nel corso del controllo di permesso sarebbe rimosso prima che il controllo di permesso successivo avvenga, a meno che l'utente autenticato non sia effettivamente membro di quel ruolo. Insieme ai fatti <literal>PermissionCheck</literal> e <literal>Role</literal> la working memory contiene anche l'oggetto <literal>java.security.Principal</literal> che era stato creato come risultato del processo di autenticazione."
+msgstr "Accanto al fatto <literal>PermissionCheck</literal> c'è anche un fatto <literal>org.jboss.seam.security.Role</literal> per ogni ruolo di cui l'utente autenticato è membro. Questi fatti <literal>Role</literal> sono sincronizzati con i ruoli dell'utente autenticato all'inizio di ogni controllo di permesso. Di conseguenza qualsiasi oggetto <literal>Role</literal> che venisse inserito nella working memory nel corso del controllo di permesso sarebbe rimosso prima che avvenga il controllo di permesso successivo, a meno che l'utente autenticato non sia effettivamente membro di quel ruolo. Insieme ai fatti <literal>PermissionCheck</literal> e <literal>Role</literal> la working memory contiene anche l'oggetto <literal>java.security.Principal</literal> che era stato creato come risultato del processo di autenticazione."

#. Tag: para
#: Security.xml:3046
@@ -4352,7 +4352,7 @@
#: Security.xml:3492
#, no-c-format
msgid "This annotation should be used when the same entity/table is used to store both user and role permissions. It identifies the property of the entity that is used to discriminate between user and role permissions. By default, if the column value contains the string literal <literal>user</literal>, then the record will be treated as a user permission. If it contains the string literal <literal>role</literal>, then it will be treated as a role permission. It is also possible to override these defaults by specifying the <literal>userValue</literal> and <literal>roleValue</literal> properties within the annotation. For example, to use <literal>u</literal> and <literal>r</literal> instead of <literal>user</literal> and <literal>role</literal>, the annotation would be written like this:"
-msgstr "Questa annotazione deve essere usata quando la stessa entità/tabella viene usata per memorizzare sia i permessi degli utenti che quelli dei ruoli. Essa identifica la proprietà dell'entità che è usata per discriminare tra i permessi degli utenti e quelli dei ruoli. Per default, se il valore della colonna contiene la stringa <literal>user</literal>, allora il record sarà trattato come un permesso utente. Se contiene la stringa <literal>role</literal>, allora sarà trattato come un permesso del ruolo. E' anche possibile sovrascrivere questi valori specificando le proprietà <literal>userValue</literal> e <literal>roleValue</literal> all'interno delle annotazioni. Ad esempio, per usere <literal>u</literal> e <literal>r</literal> invece di <literal>user</literal> e <literal>role</literal>, le annotazioni dovranno essere scritte in questo modo:"
+msgstr "Questa annotazione deve essere usata quando la stessa entità/tabella viene usata per memorizzare sia i permessi degli utenti che quelli dei ruoli. Essa identifica la proprietà dell'entità che è usata per discriminare tra i permessi degli utenti e quelli dei ruoli. Per default, se il valore della colonna contiene la stringa <literal>user</literal>, allora il record sarà trattato come un permesso utente. Se contiene la stringa <literal>role</literal>, allora sarà trattato come un permesso del ruolo. E' anche possibile sovrascrivere questi valori specificando le proprietà <literal>userValue</literal> e <literal>roleValue</literal> all'interno delle annotazioni. Ad esempio, per usare <literal>u</literal> e <literal>r</literal> invece di <literal>user</literal> e <literal>role</literal>, le annotazioni dovranno essere scritte in questo modo:"

#. Tag: programlisting
#: Security.xml:3502
@@ -4583,7 +4583,7 @@
#: Security.xml:3625
#, no-c-format
msgid "By default, multiple permissions for the same target object and recipient will be persisted as a single database record, with the <literal>action</literal> property/column containing a comma-separated list of the granted actions. To reduce the amount of physical storage required to persist a large number of permissions, it is possible to use a bitmasked integer value (instead of a comma-separated list) to store the list of permission actions."
-msgstr "Per default più permessi per lo stesso obbiettivo e destinatario vengono memorizzati un singolo record sul database, con la proprietà/colonna <literal>action</literal> contenente un elenco delle azioni concesse separate da una virgola. Per ridurre la quantità di spazio fisico richiesto per memorizzare un numero elevato di permessi è possibile usare un valore intero come maschera di bit (al posto di un elenco di valori separati da virgole) per memorizzare l'elenco delle azioni consentite."
+msgstr "Per default più permessi per lo stesso obiettivo e destinatario vengono memorizzati in un singolo record sul database, con la proprietà/colonna <literal>action</literal> contenente un elenco delle azioni concesse separate da una virgola. Per ridurre la quantità di spazio fisico richiesto per memorizzare un numero elevato di permessi è possibile usare un valore intero come maschera di bit (al posto di un elenco di valori separati da virgole) per memorizzare l'elenco delle azioni consentite."

#. Tag: para
#: Security.xml:3632
@@ -4631,7 +4631,7 @@
#: Security.xml:3655
#, no-c-format
msgid "When storing or looking up permissions, <literal>JpaPermissionStore</literal> must be able to uniquely identify specific object instances to effectively operate on its permissions. To achieve this, an <emphasis>identifier strategy</emphasis> may be assigned to each target class for the generation of unique identifier values. Each identifier strategy implementation knows how to generate unique identifiers for a particular type of class, and it is a simple matter to create new identifier strategies."
-msgstr "Quando <literal>JpaPermissionStore</literal> memorizza o cerca un permesso deve essere in grado di identificare univocamente le istanze degli oggetti sui cui permessi deve operare. Per ottenere questo occorre assegnare una <emphasis>stragegia di risoluzione dell'identificatore</emphasis> per ciascuna classe obiettivo, in modo da generare i valori identificativi univoci. Ciascuna implementazione della strategia di risoluzione sa come generare gli identificativi univoci per un particolare tipo di classe ed è solo questione di creare nuove strategia di risoluzione."
+msgstr "Quando <literal>JpaPermissionStore</literal> memorizza o cerca un permesso deve essere in grado di identificare univocamente le istanze degli oggetti sui cui permessi deve operare. Per ottenere questo occorre assegnare una <emphasis>strategia di risoluzione dell'identificatore</emphasis> per ciascuna classe obiettivo, in modo da generare i valori identificativi univoci. Ciascuna implementazione della strategia di risoluzione sa come generare gli identificativi univoci per un particolare tipo di classe ed è solo questione di creare nuove strategie di risoluzione."

#. Tag: para
#: Security.xml:3663
@@ -4833,7 +4833,7 @@
#: Security.xml:3771
#, no-c-format
msgid "The <literal>PermissionManager</literal> component is an application-scoped Seam component that provides a number of methods for managing permissions. Before it can be used, it must be configured with a permission store (although by default it will attempt to use <literal>JpaPermissionStore</literal> if it is available). To explicitly configure a custom permission store, specify the <literal>permission-store</literal> property in components.xml:"
-msgstr "Il componente <literal>PermissionManager</literal> è un componente Seam registrato a livello application che fornisce una serie di metodi per gestire i permessi. Prima di poter essere usato deve essere configurato con un permission store (benché per default tenterà di usare il <literal>JpaPermissionStore</literal> se disponibile). Per configurare esplicitamente un permission store personalizzato, occore specificare la proprietà <literal>permission-store</literal> in components.xml:"
+msgstr "Il componente <literal>PermissionManager</literal> è un componente Seam registrato a livello application che fornisce una serie di metodi per gestire i permessi. Prima di poter essere usato deve essere configurato con un permission store (benché di default tenterà di usare il <literal>JpaPermissionStore</literal> se disponibile). Per configurare esplicitamente un permission store personalizzato, occorre specificare la proprietà <literal>permission-store</literal> in components.xml:"

#. Tag: programlisting
#: Security.xml:3778
@@ -5068,7 +5068,7 @@
#: Security.xml:4147
#, no-c-format
msgid "This option helps make your system less vulnerable to sniffing of the session id or leakage of sensitive data from pages using HTTPS to other pages using HTTP."
-msgstr "Questa opzione aiuta nel rendere il sistema meno vulnerabile alle intromissioni che rilevano l'id di sessione o alla mancanza di protezione su dati sensibili dalle pagine che usano HTTPS ad altre che usano HTTP."
+msgstr "Questa opzione aiuta a rendere il sistema meno vulnerabile alle intromissioni che rilevano l'id di sessione o alla mancanza di protezione su dati sensibili dalle pagine che usano HTTPS ad altre che usano HTTP."

#. Tag: title
#: Security.xml:4153
@@ -5527,7 +5527,7 @@
#: Security.xml:4448
#, no-c-format
msgid "It's important to realize at this point that authentication does not imply authorization. The web application still needs to make a determination of how to use that information. The web application could treat the user as instantly logged in and give full access to the system or it could try and map the presented OpenID to a local user account, prompting the user to register if he hasn't already. The choice of how to handle the OpenID is left as a design decision for the local application."
-msgstr "E' importante rendersi conto, a questo punto, che l'autenticazione non implica l'autorizzazione. L'applicazione web ha ancora bisogno di fare delle determinazioni su come usare quell'informazione. L'applicazione web potrebbe trattare l'utente come immediatamente autenticato e dargli/le pieno accesso al sistema, oppure potrebbe tentare di associare l'OpenID fornito ad un utente locale, chiedendo all'utente di registrarsi se non l'ha già fatto. La scelta su come gestire l'OpenID è lasciata ad una decisione progettuale dell'applicazione locale."
+msgstr "E' importante rendersi conto, a questo punto, che l'autenticazione non implica l'autorizzazione. L'applicazione web ha ancora bisogno di fare delle considerazioni su come usare quell'informazione. L'applicazione web potrebbe trattare l'utente come immediatamente autenticato e dargli/le pieno accesso al sistema, oppure potrebbe tentare di associare l'OpenID fornito ad un utente locale, chiedendo all'utente di registrarsi se non l'ha già fatto. La scelta su come gestire l'OpenID è lasciata ad una decisione progettuale dell'applicazione locale."

#. Tag: title
#: Security.xml:4458
@@ -5647,7 +5647,7 @@
#: Security.xml:4508
#, no-c-format
msgid "Thie <literal>loginImmediately()</literal> action checks to see if the OpenID is valid. If it is valid, it adds an OpenIDPrincipal to the identity component, marks the user as logged in (i.e. <literal>#{identity.loggedIn}</literal> will be true) and returns true. If the OpenID was not validated, the method returns false, and the user re-enters the application un-authenticated. If the user's OpenID is valid, it will be accessible using the expression <literal>#{openid.validatedId}</literal> and <literal>#{openid.valid}</literal> will be true."
-msgstr "L'azione <literal>loginImmediately()</literal> controlla per vedere se l'OpenID è valido. Se è valido, aggiunge un OpenIDPrincipal al componente identity, marca l'utente come loggedin (cioè <literal>#{identity.loggedIn}</literal> sarà true) e restituisce true. Se l'OpenID non è stato validato, il metodo restituisce false, e l'utente rientra nell'applicazione non autenticato. se l'OpenID dell'utente è valido, esso sarà accessibile usando l'espressione <literal>#{openid.validatedId}</literal> e <literal>#{openid.valid}</literal> sarà true."
+msgstr "L'azione <literal>loginImmediately()</literal> controlla per vedere se l'OpenID è valido. Se è valido, aggiunge un OpenIDPrincipal al componente identity, marca l'utente come loggato (cioè <literal>#{identity.loggedIn}</literal> sarà true) e restituisce true. Se l'OpenID non è stato validato, il metodo restituisce false, e l'utente rientra nell'applicazione non autenticato. se l'OpenID dell'utente è valido, esso sarà accessibile usando l'espressione <literal>#{openid.validatedId}</literal> e <literal>#{openid.valid}</literal> sarà true."

#. Tag: title
#: Security.xml:4519
@@ -5659,7 +5659,7 @@
#: Security.xml:4521
#, no-c-format
msgid "You may not want the user to be immediately logged in to your application. In that case, your navigation should check the <literal>#{openid.valid}</literal> property and redirect the user to a local registration or processing page. Actions you might take would be asking for more information and creating a local user account or presenting a captcha to avoid programmatic registrations. When you are done processing, if you want to log the user in, you can call the <literal>loginImmediately</literal> method, either through EL as shown previously or by directly interaction with the <literal>org.jboss.seam.security.openid.OpenId</literal> component. Of course, nothing prevents you from writing custom code to interact with the Seam identity component on your own for even more customized behaviour."
-msgstr "Si può desiderare di non autenticare immediatamente l'utente nell'applicazione. In questo caso la navigazione dovrò controllare la proprietà <literal>#{openid.valid}</literal> e redirigere l'utente ad una pagina per la registrazione o l'elaborazione dell'utente. Le azioni che si possono prendere sono di chiedere maggiori informazioni e creare un utente locale, oppure presentare un CAPTCHA per evitare registrazioni da programmi automatici. Quando questa elaborazione è terminata, se si vuole autenticare l'utente è possibile chiamare il metodo <literal>loginImmediately</literal>, sia tramite EL come mostrato in precedenza, sia interagendo direttamento con il componente <literal>org.jboss.seam.security.openid.OpenId</literal>. Ovviamente niente impedisce di scrivere da soli del codice personalizzato per interagire con il componente Seam Identity per avere un comportamento più personalizzato."
+msgstr "Si può desiderare di non autenticare immediatamente l'utente nell'applicazione. In questo caso la navigazione dovrà controllare la proprietà <literal>#{openid.valid}</literal> e redirigere l'utente ad una pagina per la registrazione o l'elaborazione dell'utente. Le azioni che si possono prendere sono di chiedere maggiori informazioni e creare un utente locale, oppure presentare un CAPTCHA per evitare registrazioni da programmi automatici. Quando questa elaborazione è terminata, se si vuole autenticare l'utente è possibile chiamare il metodo <literal>loginImmediately</literal>, sia tramite EL come mostrato in precedenza, sia interagendo direttamento con il componente <literal>org.jboss.seam.security.openid.OpenId</literal>. Ovviamente niente impedisce di scrivere da soli del codice personalizzato per interagire con il componente Seam Identity per avere un comportamento più personalizzato."

#. Tag: title
#: Security.xml:4535

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits

Seam SVN: r11647 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US.

2009-11-22T10:31:23Z

Author: nico.ben
Date: 2009-11-22 13:31:22 -0500 (Sun, 22 Nov 2009)
New Revision: 11647

Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Security.xml
Log:
Some errors

Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-22 14:28:32 UTC (rev 11646)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/en-US/Security.xml 2009-11-22 18:31:22 UTC (rev 11647)
@@ -2790,9 +2790,9 @@
<h:column>
<f:facet name="header">Action</f:facet>
<s:link value="Modify Client" action="#{clientAction.modify}"
- rendered="#{s:hasPermission(cl,'modify')"/>
+ rendered="#{s:hasPermission(cl,'modify')}"/>
<s:link value="Delete Client" action="#{clientAction.delete}"
- rendered="#{s:hasPermission(cl,'delete')"/>
+ rendered="#{s:hasPermission(cl,'delete')}"/>
</h:column>
</h:dataTable>]]></programlisting>

@@ -3828,11 +3828,11 @@

<para>For example, to configure a single entity class to store both user and role permissions:</para>

- <programlisting role="XML"><![CDATA[ <security:jpa-permission-store user-permission-class="com.acme.model.AccountPermission"/>]]></programlisting>
+ <programlisting role="XML"><![CDATA[<security:jpa-permission-store user-permission-class="com.acme.model.AccountPermission"/>]]></programlisting>

<para>To configure separate entity classes for storing user and role permissions:</para>

- <programlisting role="XML"><![CDATA[ <security:jpa-permission-store user-permission-class="com.acme.model.UserPermission"
+ <programlisting role="XML"><![CDATA[<security:jpa-permission-store user-permission-class="com.acme.model.UserPermission"
role-permission-class="com.acme.model.RolePermission"/>]]></programlisting>

<sect4>
@@ -3966,7 +3966,7 @@
and <literal>role</literal>, the annotation would be written like this:
</para>

- <programlisting role="JAVA"><![CDATA[ @PermissionDiscriminator(userValue = "u", roleValue = "r")]]></programlisting>
+ <programlisting role="JAVA"><![CDATA[@PermissionDiscriminator(userValue = "u", roleValue = "r")]]></programlisting>
</entry>
</row>

_______________________________________________
seam-commits mailing list
seam-commits@...
https://lists.jboss.org/mailman/listinfo/seam-commits