[jboss-cvs] JBossAS SVN: r82101 - projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Dec 7 22:15:08 EST 2008
Author: irooskov at redhat.com
Date: 2008-12-07 22:15:08 -0500 (Sun, 07 Dec 2008)
New Revision: 82101
Modified:
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Annotations.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Cache.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Components.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Controls.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Drools.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Elenhancements.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Framework.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Groovy.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Hsearch.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/I18n.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Itext.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jbpm.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jms.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Mail.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Migration.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Persistence.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Remoting.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Security.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Spring.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Testing.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Text.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml
projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Validation.xml
Log:
went through and corrected spelling errors
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Annotations.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Annotations.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Annotations.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -221,7 +221,7 @@
<para>
Specifies the precedence of the component. If multiple
components with the same name exist, the one with the higher
- precedence will be installed. The defined precendence values
+ precedence will be installed. The defined precedence values
are (in ascending order):
</para>
@@ -240,7 +240,7 @@
</listitem>
<listitem>
<para>
- <literal>APPLICATION</literal> — Predence of
+ <literal>APPLICATION</literal> — Order of
application components (the default precedence)
</para>
</listitem>
@@ -381,20 +381,20 @@
<programlisting role="JAVA"><![CDATA[@Out]]></programlisting>
<para>
Specifies that a component attribute that is a Seam component
- is to be outjected to its context variable at the end of the
+ is to be passed to its context variable at the end of the
invocation. If the attribute is null, an exception is thrown.
</para>
<programlisting role="JAVA"><![CDATA[@Out(required=false)]]></programlisting>
<para>
Specifies that a component attribute that is a Seam component
- is to be outjected to its context variable at the end of the
+ is to be passed to its context variable at the end of the
invocation. The attribute may be null.
</para>
<programlisting role="JAVA"><![CDATA[@Out(scope=ScopeType.SESSION)]]></programlisting>
<para>
Specifies that a component attribute that is
<emphasis>not</emphasis> a Seam component type is to be
- outjected to a specific scope at the end of the invocation.
+ passed to a specific scope at the end of the invocation.
</para>
<para>
Alternatively, if no scope is explicitly specified, the scope
@@ -419,7 +419,7 @@
<para>
<literal>required</literal> — specifies Seam
should throw an exception if the component attribute is
- null during outjection.
+ null during the transfer of information.
</para>
</listitem>
</itemizedlist>
@@ -998,8 +998,7 @@
<listitem>
<programlisting role="JAVA"><![CDATA[@ApplicationException]]></programlisting>
<para>
- Synonym for javax.ejb.ApplicationException, for use in a pre
- Java EE 5 environment. Applied to an exception to denote that
+ Synonym for javax.ejb.ApplicationException, for use in a pre -Java EE 5 environment. Applied to an exception to denote that
it is an application exception and should be reported to the
client directly(i.e., unwrapped).
</para>
@@ -1035,8 +1034,7 @@
<listitem>
<programlisting role="JAVA"><![CDATA[@Interceptors({DVDInterceptor, CDInterceptor})]]></programlisting>
<para>
- Synonym for javax.interceptors.Interceptors, for use in a pre
- Java EE 5 environment. Note that this may only be used as a
+ Synonym for javax.interceptors.Interceptors, for use in a pre-Java EE 5 environment. Note that this may only be used as a
meta-annotation. Declares an ordered list of interceptors for
a class or method.
</para>
@@ -1204,7 +1202,7 @@
</section>
<section>
- <title>Annotations for asynchronicity</title>
+ <title>Annotations for asynchronously</title>
<para>
The following annotations are used to declare an asynchronous method,
for example:
@@ -1261,7 +1259,7 @@
<programlisting role="JAVA"><![CDATA[@IntervalDuration]]></programlisting>
<para>
Specifies that an asynchronous method call recurs, and that
- the annotationed parameter is duration between recurrences.
+ the annotated parameter is duration between recurrences.
</para>
</listitem>
</varlistentry>
@@ -1340,7 +1338,7 @@
<listitem>
<programlisting role="JAVA"><![CDATA[@DataModel("variableName")]]></programlisting>
<para>
- Outjects a property of type <literal>List</literal>,
+ Returns a property of type <literal>List</literal>,
<literal>Map</literal>, <literal>Set</literal> or
<literal>Object[]</literal> as a JSF
<literal>DataModel</literal> into the scope of the owning
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Cache.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Cache.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Cache.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -136,7 +136,7 @@
<para>
- For an EAR depoyment of Seam, we recommend that the JBossCache jars and
+ For an EAR deployment of Seam, we recommend that the JBossCache jars and
configuration go directly into the EAR. Make sure you place both
<literal>jboss-cache.jar</literal> and <literal>jgroups.jar</literal>
in your EAR's lib folder.
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Components.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Components.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Components.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -350,7 +350,7 @@
<listitem>
<para>
<literal>localeSelector.localeString</literal> — the
- stringified representation of the locale.
+ string representation of the locale.
</para>
</listitem>
<listitem>
@@ -409,7 +409,7 @@
<listitem>
<para>
<literal>timezoneSelector.timeZoneId</literal> — the
- stringified representation of the timezone.
+ string representation of the timezone.
</para>
</listitem>
<listitem>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -190,7 +190,7 @@
<para>
So, within a context, a component instance is identified by the context variable name (this is
- usually, but not always, the same as the component name). You may programatically access a named
+ usually, but not always, the same as the component name). You may programmatically access a named
component instance in a particular scope via the <literal>Contexts</literal> class, which provides
access to several thread-bound instances of the <literal>Context</literal> interface:
</para>
@@ -205,7 +205,7 @@
<para>
Usually, however, we obtain components from a context via injection, and put component instances into
- a context via outjection.
+ a context via querying.
</para>
</sect2>
@@ -259,7 +259,7 @@
programming model. Seam weaves a concurrency management layer into its context model.
</para>
<para>
- The Seam session and application contexts are multithreaded. Seam will allow concurrent requests in a
+ The Seam session and application contexts are multi-threaded. Seam will allow concurrent requests in a
context to be processed concurrently. The event and page contexts are by nature single threaded. The
business process context is strictly speaking multi-threaded, but in practice concurrency is
sufficiently rare that this fact may be disregarded most of the time. Finally, Seam enforces a
@@ -267,10 +267,10 @@
by serializing concurrent requests in the same long-running conversation context.
</para>
<para>
- Since the session context is multithreaded, and often contains volatile state, session scope
+ Since the session context is multi-threaded, and often contains volatile state, session scope
components are always protected by Seam from concurrent access. Seam serializes requests to session
scope session beans and JavaBeans by default (and detects and breaks any deadlocks that occur). This is
- not the default behaviour for application scoped components however, since application scoped components
+ not the default behavior for application scoped components however, since application scoped components
do not usually hold volatile state and because synchronization at the global level is
<emphasis>extremely</emphasis> expensive. However, you can force a serialized threading model on any
session bean or JavaBean component by adding the <literal>@Synchronized</literal> annotation.
@@ -646,7 +646,7 @@
<listitem>
<para>
<emphasis>bidirectional</emphasis> - values are injected from context variables into attributes of
- the component being invoked, and also <emphasis>outjected</emphasis> from the component attributes
+ the component being invoked, and also <emphasis>passed</emphasis> from the component attributes
back out to the context, allowing the component being invoked to manipulate the values of contextual
variables simply by setting its own instance variables
</para>
@@ -726,7 +726,7 @@
<para>
Injected values are disinjected (i.e, set to <literal>null</literal>) immediately after method
- completion and outjection.
+ completion and being retrived by a user.
</para>
<para>
@@ -734,7 +734,7 @@
</para>
<para>
- The <literal>@Out</literal> annotation specifies that an attribute should be outjected, either from an
+ The <literal>@Out</literal> annotation specifies that an attribute should be withdrawn, either from an
instance variable:
</para>
@@ -763,7 +763,7 @@
}]]></programlisting>
<para>
- An attribute may be both injected and outjected:
+ An attribute may be both injected and retrieved:
</para>
<programlisting role="JAVA"><![CDATA[@Name("loginAction")
@@ -869,14 +869,14 @@
<para>
The precedence of a component is a number that Seam uses to decide which component to
install when there are multiple classes with the same component name in the classpath.
- Seam will choose the component with the higher precendence. There are some predefined
+ Seam will choose the component with the higher precedence. There are some predefined
precedence values (in ascending order):
</para>
<orderedlist>
<listitem>
<para>
- <literal>BUILT_IN</literal> — the lowest precedece components are
+ <literal>BUILT_IN</literal> — the lowest precedence components are
the components built in to Seam.
</para>
</listitem>
@@ -940,7 +940,7 @@
<para>
This is nice if we are able to control exactly which classes are in the classpath. But
- if I'm writing a reusable framework with many dependecies, I don't want to have to
+ if I'm writing a reusable framework with many dependencies, I don't want to have to
break that framework across many jars. I want to be able to decide which components
to install depending upon what other components are installed, and upon what classes
are available in the classpath. The <literal>@Install</literal> annotation also
@@ -1141,7 +1141,7 @@
</para>
<para>
- The <emphasis>factory component pattern</emphasis> lets a Seam component act as the instantiator for a
+ The <emphasis>factory component pattern</emphasis> lets a Seam component act as the instigator for a
non-component object. A <emphasis>factory method</emphasis> will be called when a context variable is
referenced but has no value bound to it. We define factory methods using the <literal>@Factory</literal>
annotation. The factory method binds a value to the context variable, and determines the scope of the bound
@@ -1176,7 +1176,7 @@
<para>
A manager component is any component with an <literal>@Unwrap</literal> method. This method returns the
- value that will be visable to clients, and is called <emphasis>every time</emphasis> a context variable is
+ value that will be visible to clients, and is called <emphasis>every time</emphasis> a context variable is
referenced.
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -355,7 +355,7 @@
@Filter(within="org.jboss.seam.web.ajax4jsfFilter")
public class MultipartFilter extends AbstractFilter {]]></programlisting>
- <para> Adding the <literal>@Startup</literal> annotation means thar the component is available during
+ <para> Adding the <literal>@Startup</literal> annotation means that the component is available during
Seam startup; bijection isn't available here (<literal>@BypassInterceptors</literal>); and the filter
should be further down the chain than the RichFaces filter
(<literal>@Filter(within="org.jboss.seam.web.ajax4jsfFilter")</literal>). </para>
@@ -588,7 +588,7 @@
<para> Seam JavaBean components do not provide declarative transaction demarcation like session beans do. You
<emphasis>could</emphasis> manage your transactions manually using the JTA
- <literal>UserTransaction</literal> or declaratively using Seam's <literal>@Transactional</literal>
+ <literal>UserTransaction</literal> or decoratively using Seam's <literal>@Transactional</literal>
annotation. But most applications will just use Seam managed transactions when using Hibernate with
JavaBeans. </para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Controls.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Controls.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Controls.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -96,8 +96,8 @@
<para>
You can specify both <literal>view</literal> and
<literal>action</literal> on <literal><s:link /></literal>.
- In this case, the action wil be called once the redirect to the
- specified view has occured.
+ In this case, the action will be called once the redirect to the
+ specified view has occurred.
</para>
</section>
@@ -199,7 +199,7 @@
You can specify both <literal>view</literal> and
<literal>action</literal> on <literal><s:link /></literal>.
In this case, the action will be called once the redirect to the
- specified view has occured.
+ specified view has occurred.
</para>
</section>
@@ -577,12 +577,12 @@
<itemizedlist>
<listitem>
<para>
- <literal>style</literal> — The control's style
+ <literal>style</literal> — The controls style
</para>
</listitem>
<listitem>
<para>
- <literal>styleClass</literal> — The control's style class
+ <literal>styleClass</literal> — The controls style class
</para>
</listitem>
</itemizedlist>
@@ -938,12 +938,12 @@
</listitem>
<listitem>
<para>
- <literal>style</literal> — The control's style
+ <literal>style</literal> — The controls style
</para>
</listitem>
<listitem>
<para>
- <literal>styleClass</literal> — The control's style
+ <literal>styleClass</literal> — The controls style
class
</para>
</listitem>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -259,10 +259,10 @@
workspace management.
</para>
- <para>
+ <!-- <para>
TODO: an example to show how a nested conversation prevents bad
stuff happening when you backbutton.
- </para>
+ </para> -->
<para>
Usually, if a component exists in a parent conversation of the
@@ -1060,7 +1060,7 @@
<para>
So far we've discussed serial AJAX requests - the client tells the
- server that an event has occur, and then rerenders part of the page based
+ server that an event has occur, and then re-renders part of the page based
on the result. This approach is great when the AJAX request is
lightweight (the methods called are simple e.g. calculating the sum of a
column of numbers). But what if we need to do a complex computation?
@@ -1217,7 +1217,7 @@
<listitem>
<para>
<literal><a:poll reRender="total" interval="1000" /></literal> —
- Polls the server, and rerenders an area as needed
+ Polls the server, and re-renders an area as needed
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Drools.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Drools.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Drools.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -34,7 +34,7 @@
</para>
<para>
- If you want to use a Drools DSL, you alse need to specify the DSL
+ If you want to use a Drools DSL, you also need to specify the DSL
definition:
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Elenhancements.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Elenhancements.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Elenhancements.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -11,7 +11,7 @@
</para>
<section>
- <title>Parameterized Expressions</title>
+ <title>Parametrized Expressions</title>
<para>
Standard EL does not allow you to use a method with user defined
@@ -67,7 +67,7 @@
<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!
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Framework.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Framework.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Framework.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -534,7 +534,7 @@
<para>
Unfortunately Query objects don't work well with
<emphasis>join fetch</emphasis> queries - the use of pagination with
- these queries is not recomended, and you'll have to implement your own
+ these queries is not recommended, and you'll have to implement your own
method of calculating the total number of results (by overriding
<literal>getCountEjbql()</literal>.
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -353,7 +353,7 @@
</mediaobject>
<para>
- Then, alter the VM arguements:
+ Then, alter the VM arguments:
</para>
<mediaobject>
@@ -540,7 +540,7 @@
JBoss Tools gives you the option to either reverse engineer
entities, components and views from a database schema or to reverse
engineer components and views from existing JPA entities. We're going
- to do <emphasis>Reverse engieneer from database</emphasis>.
+ to do <emphasis>Reverse engineer from database</emphasis>.
</para>
<para>
@@ -618,7 +618,7 @@
<listitem>
<para>
- entities can never be hot-deloyed
+ entities can never be hot-deployed
</para>
</listitem>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Groovy.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Groovy.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Groovy.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -40,7 +40,7 @@
</listitem>
</itemizedlist>
- <para>TODO: write a quick overview of the Groovy syntax add-on</para>
+ <!-- <para>TODO: write a quick overview of the Groovy syntax add-on</para> -->
</section>
<section>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Hsearch.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Hsearch.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Hsearch.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -118,7 +118,7 @@
<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>
+ documentation</ulink> for more information.</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: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/I18n.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/I18n.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/I18n.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -67,7 +67,7 @@
character set to use. So you must use either ASCII characters or
escape characters not in the ASCII character set.
You can represent a Unicode character in any Java file using \uXXXX,
- where XXXX is the hexidecimal representation of the character.
+ where XXXX is the hexadecimal representation of the character.
</para>
<para>
@@ -191,7 +191,7 @@
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
- display templated labels with embedded EL expressions.</para>
+ display template labels with embedded EL expressions.</para>
<section>
<title>Defining labels</title>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Itext.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Itext.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Itext.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -1,7 +1,7 @@
<chapter id="itext">
<title>iText PDF generation</title>
<para>Seam now includes a component set for generating documents using iText. The primary focus of Seam's iText
- document support is for the generation of PDF doucuments, but Seam also offers basic support for RTF document
+ document support is for the generation of PDF documents, but Seam also offers basic support for RTF document
generation.</para>
<section id="itext.intro">
@@ -152,7 +152,7 @@
special UI components for generating suitable PDF content. Tags like
<literal><p:image></literal> and <literal><p:paragraph></literal> are the
basic foundations of simple documents. Tags like <literal><p:font></literal> provide style
- information to all the content surrounging them. </para>
+ information to all the content surrounding them. </para>
<informaltable>
@@ -643,7 +643,7 @@
<listitem>
<para>
<literal>borderWidth</literal> — The width of the border.
- Inidvidual border sides can be specified using
+ Individual border sides can be specified using
<literal>borderWidthLeft</literal>, <literal>borderWidthRight</literal>,
<literal>borderWidthTop</literal> and
<literal>borderWidthBottom</literal>.</para>
@@ -1440,7 +1440,7 @@
<listitem>
<para>
<literal>domainGridlineStroke</literal> — The stroke style of the
- domain gridleines, if visible. </para>
+ domain gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1511,7 +1511,7 @@
<listitem>
<para>
<literal>plotOutlineStroke</literal> — The stroke style of the range
- gridleines, if visible. </para>
+ gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1538,7 +1538,7 @@
<listitem>
<para>
<literal>rangeGridlineStroke</literal> — The stroke style of the range
- gridleines, if visible. </para>
+ gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1639,7 +1639,7 @@
<listitem>
<para>
<literal>domainGridlineStroke</literal> — The stroke style of the
- domain gridleines, if visible. </para>
+ domain gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1710,7 +1710,7 @@
<listitem>
<para>
<literal>plotOutlineStroke</literal> — The stroke style of the range
- gridleines, if visible. </para>
+ gridlines, if visible. </para>
</listitem>
<listitem>
@@ -1737,7 +1737,7 @@
<listitem>
<para>
<literal>rangeGridlineStroke</literal> — The stroke style of the range
- gridleines, if visible. </para>
+ gridlines, if visible. </para>
</listitem>
<listitem>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jbpm.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jbpm.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jbpm.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -44,7 +44,7 @@
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>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jms.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jms.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Jms.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -1,10 +1,10 @@
<chapter id="jms">
- <title>Asynchronicity and messaging</title>
+ <title>Asynchronous and messaging</title>
<para>
Seam makes it very easy to perform work asynchronously from a web request. When most people
- think of asynchronicity in Java EE, they think of using JMS. This is certainly one way to
+ think of asynchronous in Java EE, they think of using JMS. This is certainly one way to
approach the problem in Seam, and is the right way when you have strict and well-defined
- quality of service requirements. Seam makes it easy to send and recieve JMS messages using
+ quality of service requirements. Seam makes it easy to send and receive JMS messages using
Seam components.
</para>
@@ -32,7 +32,7 @@
</itemizedlist>
<sect1>
- <title>Asynchronicity</title>
+ <title>Asynchronously</title>
<para>
Asynchronous events and method calls have the same quality of service expectations as
@@ -97,7 +97,7 @@
</para>
<para>
- The use of asynchronicity is transparent to the bean class:
+ The use of asynchronous is transparent to the bean class:
</para>
<programlisting role="JAVA"><![CDATA[@Stateless
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Mail.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Mail.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Mail.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -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 optional components for creating templates and sending emails.
</para>
<para>
@@ -25,7 +25,7 @@
<title>Creating a message</title>
<para>
- You don't need to learn a whole new templating language to use Seam Mail
+ You don't need to learn a whole new template language to use Seam Mail
— an email is just facelet!
</para>
@@ -221,11 +221,10 @@
</section>
<section>
- <title>Templating</title>
+ <title>Templates</title>
<para>
- The mail templating example shows that facelets templating Just Works
- with the Seam mail tags.
+ The mail template example shows that facelets templates work with the Seam mail tags without effort.
</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>
@@ -310,7 +309,7 @@
requestReadReceipt="true"/>]]></programlisting>
<para>
- Otherise you can add any header to the message using the
+ Otherwise you can add any header to the message using the
<literal><m:header></literal> tag:
</para>
@@ -368,7 +367,7 @@
<para>
Each message received will cause <literal>onMessage(Message message)</literal>
to be called. Most Seam annotations will work inside a MDB but you
- musn't access the persistence context.
+ must not access the persistence context.
</para>
<para>
@@ -753,21 +752,21 @@
</para>
</listitem>
</itemizedlist>
- <para>If the value attribute is ommitted:</para>
+ <para>If the value attribute is omitted:</para>
<itemizedlist>
<listitem>
<para>
If this tag contains a <literal><p:document></literal>
tag, the document described will be generated and
attached to the email. A <literal>fileName</literal>
- should be specfied.
+ should be specified.
</para>
</listitem>
<listitem>
<para>
If this tag contains other JSF tags a HTML document will
be generated from them and attached to the email. A
- <literal>fileName</literal> should be specfied.
+ <literal>fileName</literal> should be specified.
</para>
</listitem>
</itemizedlist>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Migration.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Migration.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -394,7 +394,7 @@
</listitem>
<listitem>
<para>
- Components related to asynchronicity are located in
+ Components related to asynchronously are located in
<literal>org.jboss.seam.async</literal>
</para>
</listitem>
@@ -756,7 +756,7 @@
</listitem>
<listitem>
<para>
- Annotations related to asynchronicity are located in
+ Annotations related to asynchronously are located in
<literal>org.jboss.seam.annotations.async</literal>
</para>
<itemizedlist>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Persistence.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Persistence.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Persistence.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -303,7 +303,7 @@
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
+ transparent failover of extended persistence 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.)
</para>
@@ -445,7 +445,7 @@
<para>
Now, the <literal>claim</literal> object remains managed by the persistence context
- for the rest ot the conversation. We can make changes to the claim:
+ for the rest to the conversation. We can make changes to the claim:
</para>
<programlisting role="JAVA"><![CDATA[public void addPartyToClaim() {
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Remoting.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Remoting.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Remoting.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -310,7 +310,7 @@
remoting framework to use. </para>
<para> There are two types of client stub that can be generated, "executable" stubs and "type" stubs. Executable
- stubs are behavioural, and are used to execute methods against your session bean components, while type stubs
+ stubs are behavioral, 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
@@ -365,7 +365,7 @@
executed after starting a batch are queued, rather than being sent immediately. When all the desired component
calls have been added to the batch, the <literal>Seam.Remoting.executeBatch()</literal> method will send a single
request containing all of the queued calls to the server, where they will be executed in order. After the calls
- have been executed, a single response containining all return values will be returned to the client and the
+ have been executed, a single response containing all return values will be returned to the client and the
callback functions (if provided) triggered in the same order as execution. </para>
<para> If you start a new batch via the <literal>startBatch()</literal> method but then decide you don't want to
@@ -446,7 +446,7 @@
<para> Date values are serialized into a String representation that is accurate to the millisecond. On the client
side, use a Javascript Date object to work with date values. On the server side, use any
- <literal>java.util.Date</literal> (or descendent, such as <literal>java.sql.Date</literal> or
+ <literal>java.util.Date</literal> (or descendant, such as <literal>java.sql.Date</literal> or
<literal>java.sql.Timestamp</literal> class. </para>
</section>
@@ -528,7 +528,7 @@
<title>The Loading Message</title>
<para> The default loading message that appears in the top right corner of the screen can be modified, its rendering
- customised or even turned off completely. </para>
+ customized or even turned off completely. </para>
<section>
<title>Changing the message</title>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Security.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Security.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -1144,7 +1144,7 @@
<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
+ In plain English, this condition is stating that there must exist 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.
</para>
@@ -1350,7 +1350,7 @@
</sect2>
<sect2>
- <title>Customising the CAPTCHA algorithm</title>
+ <title>Customizing the CAPTCHA algorithm</title>
<para>
You may customize the CAPTCHA algorithm by overriding the built-in component:
@@ -1563,7 +1563,7 @@
<para>
In a similar way, the <literal>getPrincipal()</literal> or <literal>getSubject()</literal>
- methods can also be overriden to specify the <literal>Principal</literal> and
+ methods can also be overridden to specify the <literal>Principal</literal> and
<literal>Subject</literal> instances to use for the duration of the operation.
Finally, the <literal>run()</literal> method is used to carry out the
<literal>RunAsOperation</literal>.
@@ -1584,7 +1584,7 @@
<para>
The following example shows an extended Identity component with an additional
- <literal>companyCode</literal> field. The install precendence of <literal>APPLICATION</literal>
+ <literal>companyCode</literal> field. The install precedence of <literal>APPLICATION</literal>
ensures that this extended Identity gets installed in preference to the built-in Identity.
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Spring.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Spring.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Spring.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -178,7 +178,7 @@
<para> The Seam integration package also lets you use Seam's contexts as Spring 2.0 style custom scopes. This
lets you declare any Spring bean in any of Seam's contexts. However, note once again that Spring's component
- model was never architected to support statefulness, so please use this feature with great care. In
+ model was never architectured to support statefulness, so please use this feature with great care. In
particular, clustering of session or conversation scoped Spring beans is deeply problematic, and care must
be taken when injecting a bean or component from a wider scope into a bean of a narrower scope.</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Testing.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Testing.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Testing.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -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 emphasizes 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.
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Text.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Text.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Text.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -10,7 +10,7 @@
</para>
<section>
- <title>Basic fomatting</title>
+ <title>Basic formatting</title>
<para>
Here is a simple example:
</para>
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -138,7 +138,7 @@
<title>The entity bean: <literal>User.java</literal></title>
<para> We need an EJB entity bean for user data. This class defines <emphasis>persistence</emphasis> and
- <emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra
+ <emphasis>validation</emphasis> decoratively, via annotations. It also needs some extra
annotations that define the class as a Seam component. </para>
<!-- Can't use code hightlighting with callouts -->
<!-- <example>
@@ -328,12 +328,12 @@
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.
+ <para> The <literal>Log</literal> API lets us easily display log messages created from templates.
</para>
<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
+ re-displays 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
@@ -344,7 +344,7 @@
<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
+ display template error or success messages. Built-in Seam components may be
obtained by injection, or by calling an <literal>instance()</literal> method.
</para>
<!-- </example> -->
@@ -482,11 +482,11 @@
</section>
<section>
- <title>The JSF configration: <literal>faces-config.xml</literal></title>
+ <title>The JSF configuration: <literal>faces-config.xml</literal></title>
<para> Most Seam applications use JSF views as the presentation layer. So usually we'll need
<literal>faces-config.xml</literal>. In our case, we are going to use Facelets for
- defining our views, so we need to tell JSF to use Facelets as its templating engine. </para>
+ defining our views, so we need to tell JSF to use Facelets as its template engine. </para>
<!-- <example>
<title></title> -->
@@ -697,7 +697,7 @@
<literal>user</literal> component, and returns the resulting <literal>User</literal> entity bean
instance to JSF after storing it in the Seam session context. </para>
<para> The form input values are now validated against the Hibernate Validator constraints specified on the
- <literal>User</literal> entity. If the constraints are violated, JSF redisplays the page. Otherwise,
+ <literal>User</literal> entity. If the constraints are violated, JSF re-displays the page. Otherwise,
JSF binds the form input values to properties of the <literal>User</literal> entity bean. </para>
<para> Next, JSF asks Seam to resolve the variable named <literal>register</literal>. Seam finds the
<literal>RegisterAction</literal> stateless session bean in the stateless context and returns it.
@@ -866,7 +866,7 @@
}</programlisting>
- <para> The <literal>@DataModel</literal> annotation exposes an attibute of type
+ <para> The <literal>@DataModel</literal> annotation exposes an attribute 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
@@ -879,7 +879,7 @@
<para> The <literal>@Out</literal> annotation then exposes the selected value directly
to the page. So ever 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
+ and the result is subsequently <emphasis>passed</emphasis> into the event context variable
named <literal>message</literal>. </para>
<para> This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>.
@@ -1002,7 +1002,7 @@
(faces request) or a direct browser GET request (non-faces request), the page will try to resolve the
<literal>messageList</literal> context variable. Since this context variable is not initialized,
Seam will call the factory method <literal>findMessages()</literal>, which performs a query against the
- database and results in a <literal>DataModel</literal> being outjected. This
+ database and results in a <literal>DataModel</literal> being returned. This
<literal>DataModel</literal> provides the row data needed for rendering the
<literal><h:dataTable></literal>. </para>
@@ -1010,10 +1010,10 @@
<literal>select()</literal> action listener. Seam intercepts this call and injects the selected row
data into the <literal>message</literal> attribute of the <literal>messageManager</literal> component.
The action listener fires, marking the selected <literal>Message</literal> as read. At the end of the
- call, Seam outjects the selected <literal>Message</literal> to the context variable named
+ call, Seam returns the selected <literal>Message</literal> to the context variable named
<literal>message</literal>. Next, the EJB container commits the transaction, and the change to the
<literal>Message</literal> is flushed to the database. Finally, the page is re-rendered,
- redisplaying the message list, and displaying the selected message below it. </para>
+ re-displaying the message list, and displaying the selected message below it. </para>
<para> If the user clicks the <literal><h:commandButton></literal>, JSF calls the
<literal>delete()</literal> action listener. Seam intercepts this call and injects the selected row
@@ -1022,7 +1022,7 @@
<literal>remove()</literal> on the <literal>EntityManager</literal>. At the end of the call, Seam
refreshes the <literal>messageList</literal> context variable and clears the context variable named
<literal>message</literal>. The EJB container commits the transaction, and deletes the
- <literal>Message</literal> from the database. Finally, the page is re-rendered, redisplaying the
+ <literal>Message</literal> from the database. Finally, the page is re-rendered, re-displaying the
message list. </para>
</section>
@@ -1814,7 +1814,7 @@
<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
+ to make the application crash. You might think that we spent weeks testing and fixing bugs to archive
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>
@@ -2114,7 +2114,7 @@
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>
+ animated 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>
@@ -2221,7 +2221,7 @@
public void confirm()
{
em.persist(booking);
- facesMessages.add("Thank you, #{user.name}, your confimation number " +
+ facesMessages.add("Thank you, #{user.name}, your confirmation number " +
" for #{hotel.name} is #{booki g.id}");
log.info("New booking: #{booking.id} for #{user.username}");
events.raiseTransactionSuccessEvent("bookingConfirmed");
@@ -2240,7 +2240,7 @@
<para> The
<literal>@Out</literal>
- annotation declares that an attribute value is <emphasis>outjected</emphasis> to
+ annotation declares that an attribute value is <emphasis>passed</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>
@@ -2249,7 +2249,7 @@
<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
+ at the end of the request. Instead, it will be re-associated 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>
@@ -2306,7 +2306,7 @@
<section>
<title>The Seam Debug Page</title>
- <para> The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page will be availabled
+ <para> The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page will be available
if this jar is deployed in
<literal>WEB-INF/lib</literal>, along with the Facelets, and if you set the debug property
of the <literal>init</literal> component:</para>
@@ -2369,8 +2369,8 @@
</mediaobject>
</screenshot>
- <para>TODO</para>
- <para>Look in the <literal>dvdstore</literal> directory.</para>
+ <!-- <para>TODO</para>
+ <para>Look in the <literal>dvdstore</literal> directory.</para> -->
</section>
<section id="hibernate">
Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Validation.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Validation.xml 2008-12-08 01:50:27 UTC (rev 82100)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Validation.xml 2008-12-08 03:15:08 UTC (rev 82101)
@@ -163,7 +163,7 @@
<para>
That's quite a lot of functionality we need for each field
- of our form. We wouldn't want to have to specify higlighting
+ of our form. We wouldn't want to have to specify highlighting
and the layout of the image, message and input field for every
field on the form. So, instead, we'll specify the common
layout in a facelets template:
More information about the jboss-cvs-commits
mailing list