[jboss-cvs] JBossAS SVN: r86183 - in projects/docs/enterprise: 4.3.5.1/Seam/Seam_Reference_Guide/en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Mar 22 23:41:51 EDT 2009
Author: irooskov at redhat.com
Date: 2009-03-22 23:41:51 -0400 (Sun, 22 Mar 2009)
New Revision: 86183
Modified:
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml
projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Seam_Reference_Guide_CP05.xml
Log:
updated seam reference guide with translation fix
Modified: projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Seam_Reference_Guide_CP05.xml
===================================================================
--- projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Seam_Reference_Guide_CP05.xml 2009-03-23 03:37:20 UTC (rev 86182)
+++ projects/docs/enterprise/4.3.5/Seam/Reference_Guide/en-US/Seam_Reference_Guide_CP05.xml 2009-03-23 03:41:51 UTC (rev 86183)
@@ -15,10 +15,10 @@
<term><emphasis>Integrate JSF with EJB 3.0</emphasis></term>
<listitem>
<para>
- JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a brand new component model for server side business and persistence logic. Meanwhile, JSF is a great component model for the presentation tier. Unfortunately, neither component model is able to solve all problems in computing by itself. Indeed, JSF and EJB3 work best used together. But the Java EE 5 specification provides no standard way to integrate the two component models. Fortunately, the creators of both models foresaw this situation and provided standard extension points to allow extension and integration of other solutions.
+ JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a brand new component model for server side business and persistence logic. Meanwhile, JSF is a great component model for the presentation tier. Unfortunately, neither component model is able to solve all problems in computing by itself. Indeed, JSF and EJB3 work best when used together. But the Java EE 5 specification provides no standard way to integrate the two component models. Fortunately, the creators of both models anticipated this situation and provided standard extension points to allow extension and integration of other solutions.
</para>
<para>
- Seam unifies the component models of JSF and EJB3, eliminating glue code, and letting the developer think about the business problem.
+ Seam unifies the component models of JSF and EJB3, allowing the developer to concentrate on the business problem.
</para>
</listitem>
</varlistentry>
@@ -32,7 +32,7 @@
Seam also provides a built-in JavaScript remoting layer for EJB3 components. AJAX clients can easily call server-side components and subscribe to JMS topics, without the need for an intermediate action layer.
</para>
<para>
- Neither of these approaches would work well, were it not for Seam's built-in concurrency and state management, which ensures that many concurrent fine-grained, asynchronous AJAX requests are handled safely and efficiently on the server side.
+ Neither of these approaches would work well, were it not for Seam's built-in concurrency and state management, which ensures that many concurrent fine-grained, asynchronous AJAX requests are handled safely and efficiently on the server side.
</para>
</listitem>
</varlistentry>
@@ -40,24 +40,24 @@
<term><emphasis>Integrate Business Process as a First Class Construct</emphasis></term>
<listitem>
<para>
- Optionally, Seam integrates transparent business process management via jBPM. You won't believe how easy it is to implement complex workflows using jBPM and Seam.
+ Optionally, Seam integrates transparent business process management via jBPM. This allows for complex workflows to easily be implemented using jBPM and Seam.
</para>
<para>
Seam even allows definition of presentation tier conversation flow by the same means.
</para>
<para>
- JSF provides an incredibly rich event model for the presentation tier. Seam enhances this model by exposing jBPM's business process related events via exactly the same event handling mechanism, providing a uniform event model for Seam's uniform component model.
+ JSF provides an incredibly rich event model for the presentation tier. Seam enhances this model by exposing jBPM's business process related events via exactly the same event handling mechanism, providing a uniform event model for Seam's uniform component model.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><emphasis>One Kind of "Stuff"</emphasis></term>
+ <term><emphasis>The uniform component model</emphasis></term>
<listitem>
<para>
Seam provides a uniform component model. A Seam component may be stateful, with the state associated to any one of a number of contexts, ranging from the long-running business process to a single web request.
</para>
<para>
- There is no distinction between presentation tier components and business logic components in Seam. It is possible to write Seam applications where <emphasis>everything</emphasis> is an EJB. This may come as a surprise if you are used to thinking of EJBs as coarse-grained, heavyweight objects that are a pain in the backside to create! However, EJB 3.0 completely changes the nature of EJB from the point of view of the developer. An EJB is a fine-grained object - nothing more complex than an annotated JavaBean. Seam even encourages you to use session beans as JSF action listeners!
+ There is no distinction between presentation tier components and business logic components in Seam. It is possible to write Seam applications where <emphasis>everything</emphasis> is an EJB. EJB 3.0 completely changes the nature of EJB from the point of view of the developer. An EJB is a fine-grained object, no more complex than an annotated JavaBean. Seam even encourages you to use session beans as JSF action listeners.
</para>
<para>
Unlike plain Java EE or J2EE components, Seam components may <emphasis>simultaneously</emphasis> access state associated with the web request and state held in transactional resources (without the need to propagate web request state manually via method parameters). You might object that the application layering imposed upon you by the old J2EE platform was a Good Thing. Well, nothing stops you creating an equivalent layered architecture using Seam - the difference is that <emphasis>you</emphasis> get to architect your own application and decide what the layers are and how they work together.
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml 2009-03-23 03:37:20 UTC (rev 86182)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml 2009-03-23 03:41:51 UTC (rev 86183)
@@ -455,14 +455,7 @@
<entry><para>Generate basic typed composite ids</para></entry>
<entry><para>This field should always be enabled when generating the Seam CRUD application.
- A table that has a multi-colum primary key a
- <composite-id> mapping will always be created. If this
- option is enabled and there are matching foreign-keys each key
- column is still considered a 'basic' scalar (string, long, etc.)
- instead of a reference to an entity. If you disable this option
- a <key-many-to-one> instead. Note: a <many-to-one>
- property is still created, but is simply marked as non-updatable
- and non-insertable.</para></entry>
+ or a table that has a multi-colum primary key, a <composite-id> mapping will always be created. If this option is enabled and there are matching foreign-keys, each key column is still considered a basic scalar (string, long, etc.) instead of a reference to an entity. If you disable this option, a <key-many-to-one> mapping with be generated instead. Note: a <many-to-one> property is still created, but is simply marked as non-updatable and non-insertable.</para></entry>
</row>
<row>
More information about the jboss-cvs-commits
mailing list