[jboss-cvs] JBossAS SVN: r93904 - in projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide: ja-JP and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Sep 21 20:28:07 EDT 2009
Author: laubai
Date: 2009-09-21 20:28:06 -0400 (Mon, 21 Sep 2009)
New Revision: 93904
Modified:
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Jms.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Migration.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Security.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Webservices.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Xml.xml
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Migration.po
projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Persistence.po
Log:
RT#48126 Corrected Seam tags for Publican.
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Concepts.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -15,7 +15,7 @@
Let us start by describing the contexts built in to Seam.
</para>
- <sect1>
+ <section>
<title>Seam contexts</title>
<para> Seam contexts are created and destroyed by the framework. The application does not control context
demarcation via explicit Java API calls. Context are usually implicit. In some cases, however, contexts are
@@ -61,16 +61,16 @@
Let us look at each context in turn.
</para>
- <sect2>
+ <section>
<title>Stateless context</title>
<para>
Components which are truly stateless (stateless session beans, primarily) always live in the
stateless context (this is really a non-context). Stateless components are not very interesting, and are
arguably not very object-oriented. Nevertheless, they are important and often useful.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Event context</title>
<para>
The event context is the <emphasis>narrowest</emphasis> stateful context, and is a generalization of the notion of the
@@ -83,9 +83,9 @@
When you invoke a Seam component via RMI, or Seam Remoting, the event context is created and
destroyed just for the invocation.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Page context</title>
<para>
The page context allows you to associate state with a particular instance of a rendered page. You can
@@ -95,9 +95,9 @@
serialized to the client, so this construct is extremely robust with respect to multi-window operation
and the back button.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Conversation context</title>
<para>
The conversation context is a truly central concept in Seam. A <emphasis>conversation</emphasis> is a
@@ -144,9 +144,9 @@
<para>
Alternatively, Seam may be configured to keep the conversational state in the client browser.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Session context</title>
<para>
A session context holds state associated with the user login session. While there are some cases
@@ -156,9 +156,9 @@
<para>
In a JSR-168 portal environment, the session context represents the portlet session.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Business process context</title>
<para>
The business process context holds state associated with the long running business process. This
@@ -168,18 +168,18 @@
business process is defined externally using a <emphasis>process definition language</emphasis>, so
there are no special annotations for business process demarcation.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Application context</title>
<para>
The application context is the familiar servlet context from the servlet spec. Application context is
mainly useful for holding static information such as configuration data, reference data or metamodels.
For example, Seam stores its own configuration and metamodel in the application context.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Context variables</title>
<para>
A context defines a namespace, a set of <emphasis>context variables</emphasis>. These work much the
@@ -206,9 +206,9 @@
Usually, however, we obtain components from a context via injection, and place component instances into
a context via querying.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Context search priority</title>
<para>
Sometimes, as above, component instances are obtained from a particular known scope. Other times, all
@@ -241,9 +241,9 @@
Whenever you access a component by name from a JSF page, a priority search occurs.
</para>
- </sect2>
+ </section>
- <sect2 id="concurrency">
+ <section id="concurrency">
<title>Concurrency model</title>
<para>
Neither the servlet nor EJB specifications define any facilities for managing concurrent requests
@@ -278,11 +278,11 @@
This concurrency model means that AJAX clients can safely use volatile session and conversational
state, without the need for any special work on the part of the developer.
</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Seam components</title>
<para>
Seam components are POJOs (Plain Old Java Objects). In particular, they are JavaBeans or EJB 3.0
@@ -309,7 +309,7 @@
</listitem>
</itemizedlist>
- <sect2>
+ <section>
<title>Stateless session beans</title>
<para>
Stateless session bean components are not able to hold a state across multiple invocations. Therefore,
@@ -333,9 +333,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup
or the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Stateful session beans</title>
<para>
Stateful session bean components are able to hold state not only across multiple invocations of the
@@ -363,9 +363,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup
or the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Entity beans</title>
<para>
Entity beans may be bound to a context variable and function as a seam component. Because entities
@@ -398,9 +398,9 @@
to be Seam components.
</para>
</note>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>JavaBeans</title>
<para>
Javabeans may be used just like a stateless or stateful session bean. However, they do not provide
@@ -429,9 +429,9 @@
or <literal>@In(create=true)</literal>. They should not be directly instantiated using the
<literal>new</literal> operator.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Message-driven beans</title>
<para>
Message-driven beans may function as a seam component. However, message-driven beans are called quite
@@ -447,9 +447,9 @@
Message-driven beans are never instantiated by the application. They are instantiated by the EJB
container when a message is received.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Interception</title>
<para>
In order to perform bijection, context demarcation, validation, etc, Seam must intercept
@@ -482,9 +482,9 @@
</interceptor-binding>
</assembly-descriptor>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Component names</title>
<para>
All seam components need a name. We can assign a name to a component using the
@@ -551,9 +551,9 @@
name by the <literal>components.xml</literal> file included in the Seam jar.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Defining the component scope</title>
<para>
We can override the default scope (context) of a component using the <literal>@Scope</literal>
@@ -572,9 +572,9 @@
<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of possible scopes.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Components with multiple roles</title>
<para>
Some Seam component classes can fulfill more than one role in the system. For example, we often have
@@ -607,9 +607,9 @@
...
}]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Built-in components</title>
<para>
Seam is implemented mostly as a set of built-in
@@ -623,11 +623,11 @@
convenient static <literal>instance()</literal> methods:
</para>
<programlisting role="JAVA"><![CDATA[FacesMessages.instance().add("Welcome back, #{user.name}!");]]></programlisting>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Bijection</title>
<para>
<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</emphasis> is by now a familiar
@@ -801,9 +801,9 @@
...
}]]></programlisting>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Lifecycle methods</title>
<para>
@@ -837,9 +837,9 @@
specifying <literal>@Startup(depends={....})</literal>.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Conditional installation</title>
<para>
@@ -954,9 +954,9 @@
use it in your application.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Logging</title>
<para>
@@ -1024,9 +1024,9 @@
classpath, Seam with use it. If it is not, Seam will use JDK logging.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal></title>
<para>
Many application servers feature an amazingly broken implementation of <literal>HttpSession</literal>
@@ -1130,9 +1130,9 @@
</para>
</note>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Factory and manager components</title>
<para>
We often need to work with objects that are not Seam components. But we still want to be able to inject
@@ -1242,6 +1242,6 @@
on every access, a consistent view is provided.
</para>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Configuration.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -8,12 +8,12 @@
off by the following sections; you will never need to type any of this stuff yourself, since you can just copy and
paste from the example applications. </para>
- <sect1>
+ <section>
<title>Basic Seam configuration</title>
<para> First, let us look at the basic configuration that is needed whenever we use Seam with JSF. </para>
- <sect2>
+ <section>
<title>Integrating Seam with JSF and your servlet container</title>
<para>You will need a faces servlet.</para>
@@ -67,9 +67,9 @@
<param-value>true</param-value>
</context-param>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Using facelets</title>
<para> If you want follow our advice and use facelets instead of JSP, add the following lines to
@@ -86,9 +86,9 @@
<param-value>.xhtml</param-value>
</context-param>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Seam Resource Servlet</title>
<para> The Seam Resource Servlet provides resources used by Seam Remoting, captchas (see the security
@@ -104,9 +104,9 @@
<servlet-name>Seam Resource Servlet</servlet-name>
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Seam servlet filters</title>
<para> Seam does not need any servlet filters for basic operation. However, there are several features which
@@ -158,7 +158,7 @@
<para> Adding the master filter enables the following built-in filters. </para>
- <sect3>
+ <section>
<title>Exception handling</title>
<para> This filter provides the exception mapping functionality in <literal>pages.xml</literal> (almost
all applications will need this). It also takes care of rolling back uncommitted transactions when
@@ -178,9 +178,9 @@
</components>]]></programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Conversation propagation with redirects</title>
<para> This filter allows Seam to propagate the conversation context across browser redirects. It
intercepts any browser redirects and adds a request parameter that specifies the Seam conversation
@@ -190,9 +190,9 @@
in <literal>components.xml</literal>: </para>
<programlisting role="XML"><![CDATA[<web:redirect-filter url-pattern="*.seam"/>]]></programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Multipart form submissions</title>
<para> This feature is necessary when using the Seam file upload JSF control. It detects multipart form
requests and processes them according to the multipart/form-data specification (RFC-2388). To
@@ -217,9 +217,9 @@
this value, the request will be aborted. The default setting is 0 (no size limit). </para>
</listitem>
</itemizedlist>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Character encoding</title>
<para> Sets the character encoding of submitted form data. </para>
@@ -244,9 +244,9 @@
already specify an encoding. The default setting is <literal>false</literal>. </para>
</listitem>
</itemizedlist>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>RichFaces</title>
<para>
@@ -292,9 +292,9 @@
</listitem>
</itemizedlist>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Identity Logging</title>
<para>
@@ -312,9 +312,9 @@
<web:logging-filter url-pattern="*.seam"/>
</components>]]></programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Context management for custom servlets</title>
<para> Requests sent direct to some servlet other than the JSF servlet are not processed through the JSF
lifecycle, so Seam provides a servlet filter that can be applied to any other servlet that needs
@@ -339,9 +339,9 @@
Seam exposes the conversation id as a property of the built in component
<literal>conversation</literal>. </para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Adding custom filters</title>
<para> Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the
chain your filter is placed (the servlet specification doesn't provide a well defined order if you
@@ -360,10 +360,10 @@
should be further down the chain than the RichFaces filter
(<literal>@Filter(within="org.jboss.seam.web.ajax4jsfFilter")</literal>). </para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
+ <section>
<title>Integrating Seam with your EJB container</title>
<para> We need to apply the <literal>SeamInterceptor</literal> to our Seam components. The simplest way to
@@ -415,9 +415,9 @@
<programlisting role="XML"><![CDATA[<transaction:ejb-transaction/>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>The Final Item</title>
<para> There is one final item you need to know about. You must place a <literal>seam.properties</literal>,
@@ -434,11 +434,11 @@
JVM—if we did not use this mechanism, our next best option would be to force you to list every
component explicitly in <literal>components.xml</literal>.</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1 id="alt-jpa-providers">
+ <section id="alt-jpa-providers">
<title>Using Alternate JPA Providers</title>
<para> Seam comes packaged and configured with Hibernate as the default JPA provider.
@@ -479,9 +479,9 @@
file with the correct provider class, and what ever properties your
provider needs. Your new provider's jar files will need to be packaged in the application if they are needed.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in Java EE 5</title>
<mediaobject>
@@ -495,7 +495,7 @@
<para> If you are running in a Java EE 5 environment, this is all the configuration required to start using Seam. </para>
- <sect2>
+ <section>
<title>Packaging</title>
<para> Once you have packaged all this stuff together into an EAR, the archive structure will look something
@@ -560,11 +560,11 @@
<para> I really wish that was all there was to say on the topic of configuration but unfortunately we are
only about a third of the way there; feel free to skip over the rest of this section and come back to it later. </para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in J2EE</title>
<para> Seam is useful even if you are not yet ready to delve into EJB 3.0. In this case you would use
@@ -592,7 +592,7 @@
JavaBeans instead of EJB3, and another version that uses JPA and JavaBeans. These example applications are
ready to deploy into any J2EE application server. </para>
- <sect2>
+ <section>
<title>Boostrapping Hibernate in Seam</title>
<para> Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your
@@ -606,9 +606,9 @@
<programlisting role="XML"><![CDATA[<persistence:managed-hibernate-session name="hibernateSession"
session-factory="#{hibernateSessionFactory}"/>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Boostrapping JPA in Seam</title>
<para> Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your
@@ -622,9 +622,9 @@
<programlisting role="XML"><![CDATA[<persistence:managed-persistence-context name="entityManager"
entity-manager-factory="#{entityManagerFactory}"/>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Packaging</title>
<para> We can package our application as a WAR, in the following structure: </para>
@@ -664,10 +664,10 @@
<para> If we want to deploy Hibernate in a non-EE environment like Tomcat or TestNG, we need to do a little
bit more work. </para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in Java SE, without JBoss Embedded</title>
<para> It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam
@@ -684,9 +684,9 @@
<!-- <para> A better alternative is to use JBoss Embedded to get access to the EE APIs. </para>-->
- </sect1>
+ </section>
- <!--<sect1>
+ <!--<section>
<title>Configuring Seam in Java SE, with JBoss Embedded</title>
<para> JBoss Embedded lets you run EJB3 components outside the context of the Java EE 5 application server. This
@@ -715,7 +715,7 @@
</imageobject>
</mediaobject>
- <sect2 id="config.install.embedded">
+ <section id="config.install.embedded">
<title>Installing Embedded JBoss</title>
@@ -768,9 +768,9 @@
<para>For more configuration options, please see the Embedded JBoss Tomcat integration
<ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat">wiki entry</ulink>.</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Packaging</title>
<para> The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something
@@ -812,10 +812,10 @@
<para> Most of the Seam example applications may be deployed to Tomcat by running <literal>ant
deploy.tomcat</literal>. </para>
- </sect2>
- </sect1>-->
+ </section>
+ </section>-->
- <sect1>
+ <section>
<title>Configuring jBPM in Seam</title>
<para> Seam's jBPM integration is not installed by default, so you will need to enable jBPM by installing a
built-in component. You will also need to explicitly list your process and pageflow definitions. In
@@ -860,7 +860,7 @@
<para> The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should
control the JTA transactions. </para>
- <sect2>
+ <section>
<title>Packaging</title>
<para> There is not yet any well-defined packaging format for jBPM configuration and process/pageflow
@@ -910,11 +910,11 @@
approveDocument.jpdl.xml
documentLifecycle.jpdl.xml]]></programlisting>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring SFSB and Session Timeouts in JBoss AS</title>
<para> It is very important that the timeout for Stateful Session Beans is set higher than the timeout for HTTP
@@ -957,9 +957,9 @@
<para> To override this value for your own application, simply include this entry in your application's own
<literal>web.xml</literal>. </para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Running Seam in a Portlet</title>
<para>
@@ -975,6 +975,6 @@
<para>Seam Integration with JBoss Portlet Bridge is marked as technology preview, so standard support is not guaranteed.</para>
</note>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -581,14 +581,14 @@
It can be useful to redirect to an existing conversation if
the user requests the same operation twice. Take this example:
- <quote>
+ <para>
You are on Ebay, half way through paying for an item you just
won as a Christmas present for your parents. Lets say you are
sending it straight to them - you enter your payment details
but you cannot remember their address. You accidentally reuse
the same browser window finding out their address. Now you
need to return to the payment for the item.
- </quote>
+ </para>
</para>
<para>
With a natural conversation its really easy to have the user
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Jms.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Jms.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Jms.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -31,7 +31,7 @@
</listitem>
</itemizedlist>
- <sect1>
+ <section>
<title>Asynchronously</title>
<para>
@@ -69,7 +69,7 @@
same. They can just "plug and play" by adding a line to <literal>components.xml</literal>.
</para>
- <sect2>
+ <section>
<title>Asynchronous methods</title>
<para>
@@ -219,9 +219,9 @@
Asynchronous methods cannot return any other value to the caller.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Asynchronous methods with the Quartz Dispatcher</title>
<para>
@@ -336,9 +336,9 @@
<para>The <literal>@IntervalDuration</literal>, <literal>@IntervalCron</literal>, and <literal>@IntervalNthBusinessDay</literal> annotations are mutually exclusive. If they are used in the same method, a <literal>RuntimeException</literal> will be thrown.</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Asynchronous events</title>
<para>
Component-driven events may also be asynchronous. To raise an event for asynchronous
@@ -349,11 +349,11 @@
Components may observe asynchronous events in the usual way, but remember that only the
business process context is propagated to the asynchronous thread.
</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Messaging in Seam</title>
<para>
@@ -361,7 +361,7 @@
Seam components.
</para>
- <sect2>
+ <section>
<title>Configuration</title>
<para>
To configure Seam's infrastructure for sending JMS messages,
@@ -395,9 +395,9 @@
auto-create="true"
queue-jndi-name="queue/paymentQueue"/>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Sending messages</title>
<para>
Now, you can inject a JMS <literal>TopicPublisher</literal> and
@@ -438,24 +438,24 @@
}
}]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Receiving messages using a message-driven bean</title>
<para>
You can process messages using any EJB3 message driven bean. Message-driven
beans may even be Seam components, in which case it is possible to inject
other event and application scoped Seam components.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Receiving messages in the client</title>
<para>
Seam Remoting lets you subscribe to a JMS topic from client-side JavaScript. This is
described in <xref linkend="remoting"/>.
</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Migration.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Migration.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -986,7 +986,7 @@
</variablelist>
- <para>Home and Query objects are <quote>action</quote> components, not <quote>model</quote> components
+ <para>Home and Query objects are <emphasis>action</emphasis> components, not <emphasis>model</emphasis> components
and are therefore placed in the action package. This change makes the
conventions followed by generate-entities consistent with the conventions
used in the new-entity command.</para>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Security.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Security.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Security.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -8,7 +8,7 @@
for securing both domain and page resources within your Seam project.
</para>
- <sect1>
+ <section>
<title>Overview</title>
<para>
@@ -30,7 +30,7 @@
</listitem>
</itemizedlist>
- <sect2>
+ <section>
<title>Which mode is right for my application?</title>
<para>
@@ -44,10 +44,10 @@
If on the other hand, your application requires security checks based on contextual state or complex business rules,
then you will require the features provided by the advanced mode.
</para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1>
+ <section>
<title>Requirements</title>
<para>
@@ -79,9 +79,9 @@
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Disabling Security</title>
<para>
@@ -104,9 +104,9 @@
<para>Page restrictions</para>
</listitem>
</itemizedlist>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Authentication</title>
<para>
@@ -115,7 +115,7 @@
authentication requirements Seam offers a much more simplified method of authentication that hides the complexity of JAAS.
</para>
- <sect2>
+ <section>
<title>Configuration</title>
<para>
@@ -151,9 +151,9 @@
to authenticate the user.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Writing an authentication method</title>
<para>
@@ -205,7 +205,7 @@
authentication method returns <literal>false</literal> to indicate the authentication failed.
</para>
- <sect3>
+ <section>
<title>Identity.addRole()</title>
<para>
@@ -228,9 +228,9 @@
</imageobject>
</mediaobject>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Special Considerations</title>
<para>
@@ -257,11 +257,11 @@
userStats.setLastLoginDate(new Date());
userStats.incrementLoginCount();
}]]></programlisting>
- </sect3>
+ </section>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Writing a login form</title>
<para>
@@ -291,9 +291,9 @@
action will clear the security state of the currently authenticated user.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Simplified Configuration - Summary</title>
<para>
So to sum up, there are the three easy steps to configure authentication:
@@ -317,9 +317,9 @@
</listitem>
</itemizedlist>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Handling Security Exceptions</title>
<para>
@@ -375,9 +375,9 @@
Seam includes some special functionality for handling this problem.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Login Redirection</title>
<para>
@@ -420,9 +420,9 @@
the conversation in your <literal>authenticate()</literal> method.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>HTTP Authentication</title>
<para>
@@ -450,7 +450,7 @@
authentication realm that is presented to the user when they authenticate.
</para>
- <sect3>
+ <section>
<title>Writing a Digest Authenticator</title>
<para>
@@ -478,11 +478,11 @@
}
}
]]></programlisting>
- </sect3>
+ </section>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Advanced Authentication Features</title>
<para>
@@ -490,7 +490,7 @@
security requirements.
</para>
- <sect3>
+ <section>
<title>Using your container's JAAS configuration</title>
<para>
@@ -508,13 +508,13 @@
container your Seam application is deployed in. It merely instructs Seam Security to authenticate
itself using the configured JAAS security policy.
</para>
- </sect3>
+ </section>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Error Messages</title>
<para>
@@ -595,9 +595,9 @@
</tbody>
</tgroup>
</table>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Authorization</title>
<para>
@@ -608,7 +608,7 @@
above.
</para>
- <sect2>
+ <section>
<title>Core concepts</title>
<para>
@@ -626,9 +626,9 @@
for example <literal>customer:delete</literal>, or <literal>customer:insert</literal>.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Securing components</title>
<para>
@@ -636,7 +636,7 @@
<literal>@Restrict</literal> annotation.
</para>
- <sect3>
+ <section>
<title>The @Restrict annotation</title>
<para>
@@ -716,9 +716,9 @@
in <literal>Identity</literal>, which in this case can then determine if the user has the required
permission for modifying the specified <literal>Account</literal> object.
</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Inline restrictions</title>
<para>
Sometimes it might be desirable to perform a security check in code, without using the
@@ -760,10 +760,10 @@
if (!Identity.instance().hasPermission("customer", "create", null))
throw new AuthorizationException("You may not create new customers");]]></programlisting>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
+ <section>
<title>Security in the user interface</title>
<para>
@@ -824,9 +824,9 @@
</h:column>
</h:dataTable>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Securing pages</title>
<para>
Page security requires that the application is using a <literal>pages.xml</literal> file, however is
@@ -857,9 +857,9 @@
<literal>admin</literal> role.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Securing Entities</title>
<para>
@@ -988,7 +988,7 @@
your JPA provider.
</para>
- <sect3>
+ <section>
<title>Entity security with JPA</title>
<para>
@@ -1012,9 +1012,9 @@
</entity-mappings>]]></programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Entity security with a Managed Hibernate Session</title>
<para>
@@ -1023,13 +1023,13 @@
need to do anything special to use entity security.
</para>
- </sect3>
+ </section>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Writing Security Rules</title>
<para>
@@ -1038,7 +1038,7 @@
checks are processed, and how to implement permission checks for a Seam application.
</para>
- <sect2>
+ <section>
<title>Permissions Overview</title>
<para>
@@ -1049,9 +1049,9 @@
algorithms for evaluating large numbers of complex rules involving multiple conditions.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Configuring a rules file</title>
<para>
@@ -1081,9 +1081,9 @@
<para>
Once the <literal>RuleBase</literal> component is configured, it is time to write the security rules.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Creating a security rules file</title>
<para>
For this step you need to create a file called <literal>security.drl</literal> in the
@@ -1213,7 +1213,7 @@
intended for.
</para>
- <sect3>
+ <section>
<title>Wildcard permission checks</title>
<para>
@@ -1235,13 +1235,13 @@
This rule allows users with the <literal>admin</literal> role to perform <emphasis>any</emphasis> action for
any <literal>customer</literal> permission check.
</para>
- </sect3>
+ </section>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>SSL Security</title>
<para>
@@ -1297,9 +1297,9 @@
sensitive data from pages using HTTPS to other pages using HTTP.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>CAPTCHA</title>
<para>
@@ -1309,7 +1309,7 @@
prevent automated processes from interacting with your application.
</para>
- <sect2>
+ <section>
<title>Configuring the CAPTCHA Servlet</title>
<para>
To get up and running, it is necessary to configure the Seam Resource Servlet, which will provide the Captcha
@@ -1326,9 +1326,9 @@
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Adding a CAPTCHA to a form</title>
<para>
@@ -1347,9 +1347,9 @@
validated against the CAPTCHA when the form is submitted.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Customizing the CAPTCHA algorithm</title>
<para>
@@ -1376,11 +1376,11 @@
}
}]]></programlisting>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Security Events</title>
<para>
@@ -1530,9 +1530,9 @@
</tgroup>
</table>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Run As</title>
<para>
@@ -1569,9 +1569,9 @@
<literal>RunAsOperation</literal>.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Extending the Identity component</title>
<para>
@@ -1617,6 +1617,6 @@
}
}]]></programlisting>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tools.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -16,8 +16,8 @@
This tool lets you design your own business process in a graphical way.
</para>
- <screenshot>
- <screeninfo>Business process designer</screeninfo>
+ <figure>
+ <title>Business process designer</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/bpmd.png" align="center" scalefit="1"/>
@@ -26,7 +26,7 @@
<imagedata fileref="images/bpmd.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
</section>
@@ -38,8 +38,8 @@
easily share and compare ideas on how it should be designed.
</para>
- <screenshot>
- <screeninfo>Business process designer</screeninfo>
+ <figure>
+ <title>Business process designer</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/bpmpfv.png" align="center" scalefit="1"/>
@@ -48,7 +48,7 @@
<imagedata fileref="images/bpmpfv.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
</section>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Tutorial.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -1796,8 +1796,8 @@
</listitem>
</itemizedlist>
- <screenshot>
- <screeninfo>Booking example</screeninfo>
+ <figure>
+ <title>Booking example</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/booking.png" align="center" scalefit="1"/>
@@ -1806,7 +1806,7 @@
<imagedata fileref="images/booking.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
<para> The booking application uses JSF, EJB 3.0 and Seam, together with Facelets for the view. There is
also a port of this application to JSF, Facelets, Seam, JavaBeans and Hibernate3. </para>
@@ -2342,8 +2342,8 @@
<para> The user screens take advantage of a jPDL pageflow to implement searching and shopping cart
functionality. </para>
- <screenshot>
- <screeninfo>DVD Store example</screeninfo>
+ <figure>
+ <title>DVD Store example</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/dvdsearch.png" align="center" scalefit="1"/>
@@ -2352,13 +2352,13 @@
<imagedata fileref="images/dvdsearch.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
<para> The administration screens take use jBPM to manage the approval and shipping cycle for orders. The
business process may even be changed dynamically, by selecting a different process definition! </para>
- <screenshot>
- <screeninfo>DVD Store example</screeninfo>
+ <figure>
+ <title>DVD Store example</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/dvdtasks.png" align="center" scalefit="1"/>
@@ -2367,7 +2367,7 @@
<imagedata fileref="images/dvdtasks.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
<!-- <para>TODO</para>
<para>Look in the <literal>dvdstore</literal> directory.</para> -->
@@ -2393,8 +2393,8 @@
example shows how to a implement RESTful application using Seam. Every page of the application can be
bookmarked, including the search results page. </para>
- <screenshot>
- <screeninfo>Blog example</screeninfo>
+ <figure>
+ <title>Blog example</title>
<mediaobject>
<imageobject role="fo">
<imagedata fileref="images/blog.png" align="center" scalefit="1"/>
@@ -2403,7 +2403,7 @@
<imagedata fileref="images/blog.png" align="center"/>
</imageobject>
</mediaobject>
- </screenshot>
+ </figure>
<para> The Blog example demonstrates the use of "pull"-style MVC, where instead of using action listener methods
to retrieve data and prepare the data for the view, the view pulls data from components as it is being
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Webservices.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Webservices.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Webservices.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -7,7 +7,7 @@
services to run within a Seam environment.
</para>
- <sect1>
+ <section>
<title>Configuration and Packaging</title>
<para>
To allow Seam to intercept web service requests so that the necessary Seam contexts can be created for the request,
@@ -40,9 +40,9 @@
</endpoint-config>
</jaxws-config>]]></programlisting>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Conversational Web Services</title>
<para>
So how are conversations propagated between web service requests? Seam uses a SOAP header element present
@@ -89,7 +89,7 @@
As you can see, the response message contains the same <literal>conversationId</literal> element as the request.
</para>
- <sect2>
+ <section>
<title>A Recommended Strategy</title>
<para>
@@ -112,11 +112,11 @@
features to be used in the web service class itself.
</para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>An example web service</title>
<para>
@@ -196,7 +196,7 @@
and delegating the real work to a conversational Seam component.
</para>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Xml.xml
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Xml.xml 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/en-US/Xml.xml 2009-09-22 00:28:06 UTC (rev 93904)
@@ -11,7 +11,7 @@
properties file or in <literal>web.xml</literal>, and configuration via <literal>components.xml</literal>.
</para>
- <sect1>
+ <section>
<title>Configuring components via property settings</title>
<para>
Seam components may be provided with configuration properties either via servlet context parameters,
@@ -32,9 +32,9 @@
component named <literal>org.jboss.seam.core.manager</literal> with a setter method named
<literal>setConversationTimeout()</literal>.)
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring components via <literal>components.xml</literal></title>
<para>
@@ -241,9 +241,9 @@
(at development time). You'll see this approach used in the Seam examples.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Fine-grained configuration files</title>
<para>
If you have a large number of components that need to be configured in XML, it makes much more sense
@@ -282,9 +282,9 @@
Alternatively, you may put configuration for all classes in the <literal>com.helloworld</literal>
package in <literal>com/helloworld/components.xml</literal>.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configurable property types</title>
<para>
Properties of string, primitive or primitive wrapper type may be configured just as you would expect:
@@ -347,9 +347,9 @@
<property name="ruleBase">#{policyPricingRules}</property>
</component>]]></programlisting>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Using XML Namespaces</title>
<para>
Throughout the examples, there have been two competing ways of declaring components: with and without
@@ -536,7 +536,7 @@
</itemizedlist>
- </sect1>
+ </section>
</chapter>
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Migration.po
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Migration.po 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Migration.po 2009-09-22 00:28:06 UTC (rev 93904)
@@ -1796,11 +1796,11 @@
#: Migration.xml:931
#, no-c-format
msgid ""
-"Home and Query objects are <quote>action</quote> components, not "
-"<quote>model</quote> components and are therefore placed in the action "
+"Home and Query objects are action components, not "
+"model components and are therefore placed in the action "
"package. This change makes the conventions followed by generate-entities "
"consistent with the conventions used in the new-entity command."
-msgstr "Home と Query のオブジェクトは <quote>model</quote> コンポーネントではなく <quote>action</quote> コンポーネントになるため、 アクションパッケージに配置されます。 この変更により後ろに generate-entities が付く対話と new-entity コマンドで使用される対話との整合性を持たせます。"
+msgstr "Home と Query のオブジェクトは model コンポーネントではなくaction コンポーネントになるため、 アクションパッケージに配置されます。 この変更により後ろに generate-entities が付く対話と new-entity コマンドで使用される対話との整合性を持たせます。"
#. Tag: para
#: Migration.xml:936
Modified: projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Persistence.po
===================================================================
--- projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Persistence.po 2009-09-21 23:59:34 UTC (rev 93903)
+++ projects/docs/enterprise/4.3.5.1/Seam/Seam_Reference_Guide/ja-JP/Persistence.po 2009-09-22 00:28:06 UTC (rev 93904)
@@ -448,8 +448,8 @@
"ます。 <literal>#{em}</literal> は <literal>persistence:managed-persistence-"
"context</literal> コンポーネント名です。 管理永続コンテキスト名が "
"<literal>entityManager</literal> なら <literal>entity-manager</literal> 属性"
-"を省略することができます。 (<link linkend=\"persistence.seam-managed-"
-"persistence-contexts\">Seam 管理の永続コンテキスト</link> を参照)"
+"を省略することができます。 (<xref linkend=\"persistence.seam-managed-"
+"persistence-contexts\">Seam 管理の永続コンテキスト</xref> を参照)"
#. Tag: programlisting
#: Persistence.xml:243
@@ -473,9 +473,9 @@
"す。 <literal>#{hibernateSession}</literal> はプロジェクトの "
"<literal>persistence:managed-hibernate-session</literal> コンポーネント名で"
"す。 管理 Hibernate セッション名が <literal>session</literal> なら "
-"<literal>session</literal> 属性を省略することができます。 (<link linkend="
+"<literal>session</literal> 属性を省略することができます。 (<xref linkend="
"\"persistence.seam-managed-persistence-contexts\">Seam 管理の永続コンテキスト"
-"</link> を参照)"
+"</xref> を参照)"
#. Tag: programlisting
#: Persistence.xml:253
More information about the jboss-cvs-commits
mailing list