[seam-commits] Seam SVN: r14167 - branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Mon Sep 5 08:28:16 EDT 2011
Author: manaRH
Date: 2011-09-05 08:28:15 -0400 (Mon, 05 Sep 2011)
New Revision: 14167
Modified:
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Annotations.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Cache.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/ClusteringAndEJBPassivation.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Configuration.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Controls.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Conversations.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Dependencies.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Drools.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Events.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Excel.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Getting_Started_With_JBoss_Tools.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Glassfish.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/I18n.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Itext.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Jbpm.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Mail.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Persistence.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Preface.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Remoting.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Rss.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Security.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tools.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tutorial.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Validation.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Weblogic.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Websphere.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Wicket.xml
branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Xml.xml
Log:
JBSEAM-4821 - fixed typos in reference documentation
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Annotations.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Annotations.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Annotations.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -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>
@@ -965,7 +965,7 @@
<listitem>
<programlisting role="JAVA"><![CDATA[@Transition("cancel")]]></programlisting>
<para>
- Marks a method as signalling a transition in the current jBPM
+ Marks a method as signaling a transition in the current jBPM
process instance whenever the method returns a non-null
result.
</para>
@@ -1272,7 +1272,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 annotation parameter is duration between recurrences.
</para>
</listitem>
</varlistentry>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Cache.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Cache.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Cache.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -265,7 +265,7 @@
</tip>
<para>
- For an EAR depoyment of Seam, we recommend that the cache jars and
+ For an EAR deployment of Seam, we recommend that the cache jars and
configuration go directly into the EAR.
</para>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/ClusteringAndEJBPassivation.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/ClusteringAndEJBPassivation.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/ClusteringAndEJBPassivation.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -137,7 +137,7 @@
</listitem>
<listitem>
<para>Ensure you have two IP addresses available (two computers, two network cards, or two IP
- addressses bound to the same interface). I'll assume the two IP address are 192.168.1.2 and
+ addresses bound to the same interface). I'll assume the two IP address are 192.168.1.2 and
192.168.1.3</para>
</listitem>
<listitem>
@@ -209,7 +209,7 @@
<para>
So you can see that at least both servers claim to have identical sessions. Now, time to test that the
- data is serializing and unserializing properly.
+ data is serializing and deserializing properly.
</para>
<para>
@@ -265,7 +265,7 @@
The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish
the same overall goal. It ensures that throughout the life of a conversation using at least one extended
persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not
- become detached prematurally by a passivation event). In short, it ensures the integrity of the extended
+ become detached prematurely by a passivation event). In short, it ensures the integrity of the extended
persistence context (and therefore its guarantees).
</para>
@@ -302,7 +302,7 @@
<para>
Database-oriented applications do much more than just read from and write to the database. They capture
- transactional bits of information that need to be tranfered into the database atomically (at once). It's
+ transactional bits of information that need to be transferred into the database atomically (at once). It's
not always possible to capture this information all on one screen. Additionally, the user might need to
make a judgement call about whether to approve or reject the pending changes.
</para>
@@ -385,16 +385,16 @@
<para>
Dealing with passivation of a SFSB works by leveraging the HTTP session. But what happens when the HTTP
session passivates? This happens in a clustered environment with session replication enabled. This case
- is much tricker to deal with and is where a bulk of the MEI infrastructure comes into play. In thise
+ is much tricker to deal with and is where a bulk of the MEI infrastructure comes into play. In this
case, the persistence manager is going to be destroyed because it cannot be serialized. Seam handles
this deconstruction (hence ensuring that the HTTP session serializes properly). But what happens on the
other end. Well, when the MEI sticks an entity instance into the conversation, it embeds the instance in
- a wrapper that provides information on how to reassociate the instance with a persistence manager
+ a wrapper that provides information on how to re-associate the instance with a persistence manager
post-serialization. So when the application jumps to another node in the cluster (presumably because the
- target node went down) the MEI infrastruture essentially reconstructs the persistence context. The huge
+ target node went down) the MEI infrastructure essentially reconstructs the persistence context. The huge
drawback here is that since the persistence context is being reconstructed (from the database), pending
changes are dropped. However, what Seam does do is ensure that if the entity instance is versioned, that
- the guarantees of optimistic locking are upheld. (why isn't the dirty state transfered?)
+ the guarantees of optimistic locking are upheld. (why isn't the dirty state transferred?)
</para>
<note>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Concepts.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -65,7 +65,7 @@
<title>Stateless context</title>
<para>
Components which are truly stateless (stateless session beans, primarily) always live in the stateless
- context (which is basically the absense of a context since the instance Seam resolves is not stored).
+ context (which is basically the absence of a context since the instance Seam resolves is not stored).
Stateless components are not very interesting, and are arguably not very object-oriented. Nevertheless,
they do get developed and used and are thus an important part of any Seam application.
</para>
@@ -191,7 +191,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>
@@ -250,7 +250,7 @@
<para>
Neither the servlet nor EJB specifications define any facilities for managing concurrent requests
originating from the same client. The servlet container simply lets all threads run concurrently and
- leaves enforcing threadsafeness to application code. The EJB container allows stateless components to be
+ leaves enforcing thread safeness to application code. The EJB container allows stateless components to be
accessed concurrently, and throws an exception if multiple threads access a stateful session bean.
</para>
<para>
@@ -410,7 +410,7 @@
<sect2>
<title>JavaBeans</title>
<para>
- Javabeans may be used just like a stateless or stateful session bean. However, they do not provide
+ JavaBeans may be used just like a stateless or stateful session bean. However, they do not provide
the functionality of a session bean (declarative transaction demarcation, declarative security,
efficient clustered state replication, EJB 3.0 persistence, timeout methods, etc).
</para>
@@ -906,14 +906,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>
@@ -977,7 +977,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
@@ -1213,7 +1213,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: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Configuration.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Configuration.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Configuration.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -417,7 +417,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>
@@ -549,7 +549,7 @@
When Seam attempts to find another Seam EJB component to satisfy an injection point defined using
<literal>@In</literal>, whether or not it finds it depends on whether an EJB reference exists in
JNDI. Strictly speaking, you cannot simply resolve JNDI names as you please. You have to define
- the references explicitly. Fortunately, JBoss recognized how aggrevating this would be for the
+ the references explicitly. Fortunately, JBoss recognized how aggravating this would be for the
developer and all versions of JBoss automatically register EJBs so they are always available in
JNDI, both to the web container and the EJB container. So if you are using JBoss, you can skip the next
few paragraphs. However, if you are deploying to GlassFish, pay close attention.</para>
@@ -588,7 +588,7 @@
<para> Notice that the contents of the <literal><ejb-local-ref></literal> are identical to what we
defined in web.xml. What we are doing is bringing the reference into the EJB context where it can be
used by the RegisterAction bean. You will need to add one of these references for any injection of a
- Seam EJB compoenent into another Seam EJB component using <literal>@In</literal>. (You can see an
+ Seam EJB component into another Seam EJB component using <literal>@In</literal>. (You can see an
example of this setup in the jee5/booking example).</para>
<para> But what about <literal>@EJB</literal>? It's true that you can inject one EJB into another using
@@ -661,7 +661,7 @@
</para>
</note>
- <para>Telling seam about a different JPA provider can be be done in one of two ways:</para>
+ <para>Telling seam about a different JPA provider can be done in one of two ways:</para>
<para>Update your application's <literal>components.xml</literal>
so that the generic <literal>PersistenceProvider</literal> takes
precedence over the hibernate version. Simply add the following
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Controls.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Controls.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Controls.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -105,7 +105,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>
<para>
@@ -1228,7 +1228,7 @@
<para><emphasis>Description</emphasis></para>
<para>
A tag that acts a file download provider. It must be alone in the JSF page.
- To be able to use this contol, web.xml must be set up as follows.
+ To be able to use this control, web.xml must be set up as follows.
</para>
<para><emphasis>Configuration</emphasis></para>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Conversations.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Conversations.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Conversations.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -1158,7 +1158,7 @@
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 thats going to take a minute?
+ a complex computation that is going to take a minute?
</para>
<para>
@@ -1288,7 +1288,7 @@
<para>
Alternatively, you can allow RichFaces handle the error, in which
case the user will be presented with a prompt that reads "View state
- could't be restored - reload page?" You can customize this message
+ couldn't be restored - reload page?" You can customize this message
globally by setting the following message key in an application
resource bundle.
</para>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Dependencies.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Dependencies.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Dependencies.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -706,7 +706,7 @@
<para>war</para>
</entry>
<entry>
- <para>Apache HTTP Client libraies</para>
+ <para>Apache HTTP Client libraries</para>
</entry>
</row>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Drools.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Drools.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Drools.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -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: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Events.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Events.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Events.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -379,7 +379,7 @@
<title>Conversion and Validation</title>
<para>
- You can specify a JSF converter for complex model propreties:
+ You can specify a JSF converter for complex model properties:
</para>
<programlisting role="XML"><![CDATA[<pages>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Excel.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Excel.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Excel.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -498,7 +498,7 @@
<para>
<literal>defaultRowHeight</literal>
— The default row height. The value is a
- number (1/20ths of a point).
+ number (1/20 of a point).
</para>
</listitem>
<listitem>
@@ -709,7 +709,7 @@
<listitem>
<para>
<literal>verticalCentre</literal>
- — Center verically? The value is a boolean.
+ — Center vertically? The value is a boolean.
</para>
</listitem>
<listitem>
@@ -1708,7 +1708,7 @@
<section id="excel.headersfooters">
<title>Headers and footers</title>
<para>
- Headers and footers are childrens of worksheets and contain facets which
+ Headers and footers are children of worksheets and contain facets which
in turn contains a string with commands that are parsed.
</para>
<informaltable>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Getting_Started_With_JBoss_Tools.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Getting_Started_With_JBoss_Tools.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Getting_Started_With_JBoss_Tools.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -367,7 +367,7 @@
</mediaobject>
<para>
- Then, alter the VM arguements:
+ Then, alter the VM arguments:
</para>
<mediaobject>
@@ -554,7 +554,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 engineering from database</emphasis>.
</para>
<para>
@@ -632,7 +632,7 @@
<listitem>
<para>
- entities can never be hot-deloyed
+ entities can never be hot-deployed
</para>
</listitem>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Glassfish.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Glassfish.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Glassfish.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -73,7 +73,7 @@
The web administration console is available at <literal>http://localhost:4848/</literal>.
You can access the web admin console with the default username
(<literal>admin</literal>) and password (<literal>adminadmin</literal>).
- We will be using the the admin console to deploy our examples.
+ We will be using admin console to deploy our examples.
You can also copy EAR/WAR files to the
<literal>glassfish/domains/domain1/autodeploy</literal> directory
to deploy them, although we are not going to cover that.
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/I18n.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/I18n.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/I18n.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -71,7 +71,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>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Itext.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Itext.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Itext.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -875,7 +875,7 @@
<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. The
- following document uses the <literal>ui:repeat</literal> tag to to display a list of values retrieved
+ following document uses the <literal>ui:repeat</literal> tag to display a list of values retrieved
from a Seam component. </para>
<programlisting role="XHTML"><![CDATA[<p:document xmlns:p="http://jboss.com/products/seam/pdf"
@@ -1374,7 +1374,7 @@
<literal>red</literal>, <literal>pink</literal>, <literal>yellow</literal>,
<literal>green</literal>, <literal>magenta</literal>, <literal>cyan</literal> and
<literal>blue</literal>. Colors can be specified as an integer value, as
- definied by <literal>java.awt.Color</literal>. Finally a color value may be specified
+ defined by <literal>java.awt.Color</literal>. Finally a color value may be specified
as <literal>rgb(r,g,b)</literal> or <literal>rgb(r,g,b,a)</literal> with the red, green, blue
alpha values specified as an integer between 0 and 255 or as a floating point percentages
followed by a '%' sign.
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Jbpm.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Jbpm.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Jbpm.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -49,7 +49,7 @@
</para>
<para>
- You don't have to know jDPL to use Seam. If you're perfectly happy defining
+ You don't have to know jPDL to use Seam. If you're perfectly happy defining
pageflow using JSF or Seam navigation rules, and if your application is more
data-driven that process-driven, you probably don't need jBPM. But we're
finding that thinking of user interaction in terms of a well-defined graphical
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Mail.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Mail.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Mail.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -258,7 +258,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).
@@ -367,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>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Persistence.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Persistence.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Persistence.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -67,7 +67,7 @@
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
+ complex applications, with many loosely-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
@@ -147,7 +147,7 @@
<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
+ apply request values phase) until the end of the invoke application phase; the second spans the
render response phase
</para>
</listitem>
@@ -275,7 +275,7 @@
Seam transaction component when committing a transaction to ensure synchronization callbacks are
correctly executed. If in a Java EE 5 environment the
<literal><transaction:ejb-transaction/></literal>
- component should be be declared in <literal>components.xml</literal> to ensure that Seam synchronization callbacks are
+ component should be declared in <literal>components.xml</literal> to ensure that Seam synchronization callbacks are
correctly called if the container commits a transaction outside of Seam's knowledge.
</para>
</section>
@@ -305,7 +305,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>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Preface.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Preface.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Preface.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -102,7 +102,7 @@
<listitem>
<para>
Optionally, Seam provides transparent business process management via jBPM. You won't
- believe how easy it is to implement complex workflows, collaboration and and task management
+ believe how easy it is to implement complex workflows, collaboration and task management
using jBPM and Seam.
</para>
<para>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Remoting.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Remoting.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Remoting.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -374,7 +374,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 containning 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
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Rss.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Rss.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Rss.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -124,7 +124,7 @@
</listitem>
</itemizedlist>
<para>
- <emphasis>Child elemenents</emphasis>
+ <emphasis>Child elements</emphasis>
</para>
<itemizedlist>
<listitem>
@@ -223,7 +223,7 @@
</listitem>
</itemizedlist>
<para>
- <emphasis>Child elemenents</emphasis>
+ <emphasis>Child elements</emphasis>
</para>
<itemizedlist>
<listitem>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Security.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Security.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Security.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -341,7 +341,7 @@
which should be a short timespan. However, it is much more attractive and dangerous if an attacker has the possibility
to steal a persistent Remember Me cookie that allows him to login without authentication, at any time. Note that this
all depends on how well you protect your website against XSS attacks - it's up to you to make sure that your website
- is 100% XSS safe - a non-trival achievement for any website that allows user input to be rendered on a page.
+ is 100% XSS safe - a non-trivial achievement for any website that allows user input to be rendered on a page.
</para>
<para>
@@ -2880,7 +2880,7 @@
<para>
It is also possible to only restrict certain actions, by placing a <literal>@Restrict</literal> annotation
- on the relevent entity lifecycle method (annotated as follows):
+ on the relevant entity lifecycle method (annotated as follows):
</para>
<itemizedlist>
@@ -3088,7 +3088,7 @@
}]]></programlisting>
<para>
- If you wish to override the default permisison action name (which is the lower case version of the annotation name) with
+ If you wish to override the default permission action name (which is the lower case version of the annotation name) with
another value, you can specify it within the <literal>@PermissionCheck</literal> annotation:
</para>
@@ -5026,7 +5026,7 @@
Sometimes it might be necessary to extend the Identity component if your application has
special security requirements. The following example (contrived, as credentials would normally
be handled by the <literal>Credentials</literal> component instead) shows an extended Identity
- component with an additional <literal>companyCode</literal> field. The install precendence of <literal>APPLICATION</literal>
+ component with an additional <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>
@@ -5078,7 +5078,7 @@
OpenID is a community standard for external web-based authentication. The basic
idea is that any web application can supplement (or replace) its local handling of
authentication by delegating responsibility to an external OpenID server of the user's
- chosing. This benefits the user, who no longer has to remember a name and password for
+ choose. This benefits the user, who no longer has to remember a name and password for
every web application he uses, and the developer, who is relieved of some of the burden of
maintaining a complex authentication system.
</para>
@@ -5170,7 +5170,7 @@
</navigation>
</page></programlisting>
- <para>Thie <literal>loginImmediately()</literal> action checks to see if the OpenID is valid. If it is valid, it adds an
+ <para>This <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
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tools.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tools.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tools.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -71,7 +71,7 @@
</para>
<para>
- The following sections is focused on the features required to understand for usage with Seam. The content is derived from the the Hibernate Tools reference documentation. Thus if you
+ The following sections is focused on the features required to understand for usage with Seam. The content is derived from the Hibernate Tools reference documentation. Thus if you
need more detailed information please refer to the Hibernate Tools documentation.
</para>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tutorial.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tutorial.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Tutorial.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -49,7 +49,7 @@
installation, to the location of your JBoss AS installation.</para>
<para>Once you've set the location of JBoss AS and started the application server, you can build and deploy
- any example by typing <literal>ant explode</literal> in the the directory for that example. Any example
+ any example by typing <literal>ant explode</literal> in the directory for that example. Any example
that is packaged as an EAR deploys to a URL like
<literal>/seam-<replaceable>example</replaceable></literal>, where <replaceable>example</replaceable> is
the name of the example folder, with one exception. If the example folder begins with seam, the prefix
@@ -594,7 +594,7 @@
</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
@@ -931,7 +931,7 @@
}]]></programlisting>
<calloutlist>
<callout arearefs="messages-datamodel">
- <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
@@ -1501,7 +1501,7 @@
<literal>todoList</literal> component
knows which task the button is for because each s:button specificies
<literal>taskInstance="#{task}"</literal>, referring
- to the task for that particular line of of the table. The <literal>@StartTast</literal> and
+ to the task for that particular line of the table. The <literal>@StartTast</literal> and
<literal>@EndTask</literal> annotations
cause seam to make the task active and immediately complete the task. The original process then
transitions into the <literal>done</literal> state, according to the process definition, where it ends.
@@ -1935,7 +1935,7 @@
more guesses. If there are more guesses (<literal>lastGuess</literal> is <literal>false</literal>),
we transition back to the original <literal>displayGuess</literal> state. Finally we've
reached a page state, so the associated page <literal>/numberGuess.jspx</literal> is displayed.
- Since the page has a redirect element, Seam sends a redirect to the the user's browser,
+ Since the page has a redirect element, Seam sends a redirect to the user's browser,
starting the process over.
</para>
@@ -2017,7 +2017,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 achieve
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>
@@ -3188,7 +3188,7 @@
</para>
<para>Just like with page parameters, URL rewriting is bi-directional. That means that Seam
- forwards requests for the simpler URL to the the right view, and it also automatically generates
+ forwards requests for the simpler URL to the right view, and it also automatically generates
the simpler view for you. You never need to worry about constructing URLs. It's
all handled transparently behind the scenes. The only requirement is that to use URL rewriting,
the rewrite filter needs to be enabled in <literal>components.xml</literal>.
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Validation.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Validation.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Validation.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -161,7 +161,7 @@
<para>
You can then inject this value into the message string using
the placeholder {0} (the first and only parameter passed to a
- JSF message for a Hiberate Validator restriction). See the
+ JSF message for a Hibernate Validator restriction). See the
internationalization section for more information regarding
where to define these messages.
</para>
@@ -180,7 +180,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:
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Weblogic.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Weblogic.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Weblogic.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -82,7 +82,7 @@
for an account with Oracle in order to do this. </para>
</listitem>
<listitem>
- <para> You may need to change the the
+ <para> You may need to change the
<literal>server103_XX.bin</literal> file to be
executable: </para>
<programlisting>chmod a+x server103_XX.bin</programlisting>
@@ -952,7 +952,7 @@
<title>What's different with Weblogic 10.x</title>
<itemizedlist>
<listitem>
- <para>Between the the Weblogic 10.x and 9.2 examples there are
+ <para>Between the Weblogic 10.x and 9.2 examples there are
several differences:
</para>
<itemizedlist>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Websphere.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Websphere.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Websphere.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -349,7 +349,7 @@
<listitem>
Log in to the administration console
<programlisting><![CDATA[http://localhost:9060/admin]]></programlisting>
- Enter your userid annd/or your password if security is enabled for the console.
+ Enter your userid and/or your password if security is enabled for the console.
</listitem>
<listitem>
@@ -529,7 +529,7 @@
<listitem>
<para>
<literal>import.sql</literal>
- — due to the cutomized hibernate Derby dialect, the <literal>ID</literal>
+ — due to the customized hibernate Derby dialect, the <literal>ID</literal>
column can not be populated by this file and was removed.
</para>
</listitem>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Wicket.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Wicket.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Wicket.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -218,7 +218,7 @@
</section>
<section>
<title>Runtime instrumentation agent</title>
- <para>The jar file <literal>jboss-seam-wicket.jar</literal> can be used as an iinstrumentation
+ <para>The jar file <literal>jboss-seam-wicket.jar</literal> can be used as an instrumentation
agent through the Java Instrumentation api. This is accomplished through the following
steps:</para>
<itemizedlist>
Modified: branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Xml.xml
===================================================================
--- branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Xml.xml 2011-09-05 12:27:11 UTC (rev 14166)
+++ branches/community/Seam_2_3/seam-reference-guide/src/docbook/en-US/Xml.xml 2011-09-05 12:28:15 UTC (rev 14167)
@@ -428,7 +428,7 @@
validated at development time.
</para>
- <para>The namespaced version looks like this:</para>
+ <para>The version with using namespaces looks like this:</para>
<programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<components xmlns="http://jboss.com/products/seam/components"
@@ -549,7 +549,7 @@
be used for guidance.
</para>
- <para>The following are the the namespaces used by Seam:</para>
+ <para>The following are the namespaces used by Seam:</para>
<itemizedlist>
<listitem>
More information about the seam-commits
mailing list