[seam-commits] Seam SVN: r11724 - branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Fri Dec 4 02:54:45 EST 2009
Author: laubai
Date: 2009-12-04 02:54:45 -0500 (Fri, 04 Dec 2009)
New Revision: 11724
Modified:
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Concepts.xml
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Configuration.xml
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Jms.xml
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Security.xml
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Webservices.xml
branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Xml.xml
Log:
Replaced sect# with section tags for publican build.
Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Concepts.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Concepts.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Concepts.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -16,7 +16,7 @@
Let's start by describing the contexts built in to Seam.
</para>
- <sect1>
+ <section>
<title>Seam contexts</title>
<para> Seam contexts are created and destroyed by the framework. The application does not control context
demarcation via explicit Java API calls. Context are usually implicit. In some cases, however, contexts are
@@ -62,16 +62,16 @@
Let's look at each context in turn.
</para>
- <sect2>
+ <section>
<title>Stateless context</title>
<para>
Components which are truly stateless (stateless session beans, primarily) always live in the
stateless context (this is really a non-context). Stateless components are not very interesting, and are
arguably not very object-oriented. Nevertheless, they are important and often useful.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Event context</title>
<para>
The event context is the "narrowest" stateful context, and is a generalization of the notion of the
@@ -84,9 +84,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
@@ -96,9 +96,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
@@ -146,9 +146,9 @@
<para>
Alternatively, Seam may be configured to keep conversational state in the client browser.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Session context</title>
<para>
A session context holds state associated with the user login session. While there are some cases
@@ -158,9 +158,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
@@ -170,18 +170,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
@@ -208,9 +208,9 @@
Usually, however, we obtain components from a context via injection, and put component instances into
a context via outjection.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Context search priority</title>
<para>
Sometimes, as above, component instances are obtained from a particular known scope. Other times, all
@@ -243,9 +243,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
@@ -280,11 +280,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
@@ -311,7 +311,7 @@
</listitem>
</itemizedlist>
- <sect2>
+ <section>
<title>Stateless session beans</title>
<para>
Stateless session bean components are not able to hold state across multiple invocations. Therefore,
@@ -335,9 +335,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
@@ -365,9 +365,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 @@
Seam entity bean components may be instantiated using <literal>Component.getInstance()</literal>,
<literal>@In(create=true)</literal> or directly using the <literal>new</literal> operator.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>JavaBeans</title>
<para>
Javabeans may be used just like a stateless or stateful session bean. However, they do not provide
@@ -424,9 +424,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
@@ -442,9 +442,9 @@
Message-driven beans are never instantiated by the application. They are instantiated by the EJB
container when a message is received.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Interception</title>
<para>
In order to perform its magic (bijection, context demarcation, validation, etc), Seam must intercept
@@ -477,9 +477,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
@@ -546,9 +546,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>
@@ -567,9 +567,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
@@ -602,9 +602,9 @@
...
}]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Built-in components</title>
<para>
Like many good frameworks, Seam eats its own dogfood and is implemented mostly as a set of built-in
@@ -618,11 +618,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
@@ -796,9 +796,9 @@
...
}]]></programlisting>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Lifecycle methods</title>
<para>
@@ -832,9 +832,9 @@
specifying <literal>@Startup(depends={....})</literal>.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Conditional installation</title>
<para>
@@ -950,9 +950,9 @@
use it in your application.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Logging</title>
<para>
@@ -1025,9 +1025,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>
@@ -1129,9 +1129,9 @@
of managing an entity bean instance using a Seam component.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Factory and manager components</title>
<para>
We often need to work with objects that are not Seam components. But we still want to be able to inject
@@ -1241,6 +1241,6 @@
on every access, a consistent view is provided.
</para>
- </sect1>
+ </section>
</chapter>
Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Configuration.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Configuration.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Configuration.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -9,12 +9,12 @@
off by the following sections; you'll never need to type any of this stuff yourself, since you can just copy and
paste from the example applications! </para>
- <sect1>
+ <section>
<title>Basic Seam configuration</title>
<para> First, let's look at the basic configuration that is needed whenever we use Seam with JSF. </para>
- <sect2>
+ <section>
<title>Integrating Seam with JSF and your servlet container</title>
<para> Of course, you need a faces servlet! </para>
@@ -68,9 +68,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
@@ -87,9 +87,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
@@ -105,9 +105,9 @@
<servlet-name>Seam Resource Servlet</servlet-name>
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Seam servlet filters</title>
<para> Seam doesn't need any servlet filters for basic operation. However, there are several features which
@@ -159,7 +159,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
@@ -179,9 +179,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
@@ -191,9 +191,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
@@ -218,9 +218,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>
@@ -245,9 +245,9 @@
already specify an encoding. The default setting is <literal>false</literal>. </para>
</listitem>
</itemizedlist>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>RichFaces</title>
<para>
@@ -293,9 +293,9 @@
</listitem>
</itemizedlist>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Identity Logging</title>
<para>
@@ -313,9 +313,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
@@ -340,9 +340,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
@@ -361,10 +361,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>Don't forget!</title>
<para> There is one final item you need to know about. You must place a <literal>seam.properties</literal>,
@@ -437,11 +437,11 @@
component explicitly in <literal>components.xml</literal>, just like some other competing frameworks do!
I think you'll like our way better. </para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1 id="alt-jpa-providers">
+ <section id="alt-jpa-providers">
<title>Using Alternate JPA Providers</title>
<para> Seam comes packaged and configured with Hibernate as the default JPA provider.
@@ -483,9 +483,9 @@
provider needs. Don't forget to package your new provider's jar files in the
application if they are needed.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in Java EE 5</title>
<mediaobject>
@@ -499,7 +499,7 @@
<para> If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam! </para>
- <sect2>
+ <section>
<title>Packaging</title>
<para> Once you've packaged all this stuff together into an EAR, the archive structure will look something
@@ -565,11 +565,11 @@
only about a third of the way there. If you're too overwhelmed by all this tedious configuration stuff,
feel free to skip over the rest of this section and come back to it later. </para>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in J2EE</title>
<para> Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. In this case you would use
@@ -597,7 +597,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
@@ -611,9 +611,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
@@ -627,9 +627,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>
@@ -669,10 +669,10 @@
<para> If we want to deploy Hibernate in a non-EE environment like TestNG, we need to do a little
bit more work. </para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1>
+ <section>
<title>Configuring Seam in Java SE, without JBoss Embedded</title>
<para> It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam
@@ -686,9 +686,9 @@
<programlisting role="XML"><![CDATA[<transaction:hibernate-transaction session="#{session}"/>]]></programlisting>
<para> Of course, you'll also need to define a datasource.</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Configuring jBPM in Seam</title>
<para> Seam's jBPM integration is not installed by default, so you'll need to enable jBPM by installing a
built-in component. You'll also need to explicitly list your process and pageflow definitions. In
@@ -733,7 +733,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
@@ -783,11 +783,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
@@ -830,9 +830,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>
@@ -848,6 +848,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: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Jms.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Jms.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Jms.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -35,7 +35,7 @@
</listitem>
</itemizedlist>
- <sect1>
+ <section>
<title>Asynchronicity</title>
<para>
@@ -73,7 +73,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>
@@ -223,9 +223,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>
@@ -340,9 +340,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
@@ -353,11 +353,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>
@@ -365,7 +365,7 @@
Seam components.
</para>
- <sect2>
+ <section>
<title>Configuration</title>
<para>
To configure Seam's infrastructure for sending JMS messages,
@@ -399,9 +399,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
@@ -442,24 +442,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: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Security.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Security.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Security.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -10,7 +10,7 @@
for securing both domain and page resources within your Seam project.
</para>
- <sect1>
+ <section>
<title>Overview</title>
<para>
@@ -32,7 +32,7 @@
</listitem>
</itemizedlist>
- <sect2>
+ <section>
<title>Which mode is right for my application?</title>
<para>
@@ -46,10 +46,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>
@@ -81,9 +81,9 @@
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Disabling Security</title>
<para>
@@ -106,9 +106,9 @@
<para>Page restrictions</para>
</listitem>
</itemizedlist>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Authentication</title>
<para>
@@ -117,7 +117,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>
@@ -153,9 +153,9 @@
to authenticate the user.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Writing an authentication method</title>
<para>
@@ -207,7 +207,7 @@
authentication method returns <literal>false</literal> to indicate the authentication failed.
</para>
- <sect3>
+ <section>
<title>Identity.addRole()</title>
<para>
@@ -230,9 +230,9 @@
</imageobject>
</mediaobject>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Special Considerations</title>
<para>
@@ -259,11 +259,11 @@
userStats.setLastLoginDate(new Date());
userStats.incrementLoginCount();
}]]></programlisting>
- </sect3>
+ </section>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Writing a login form</title>
<para>
@@ -293,9 +293,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:
@@ -319,9 +319,9 @@
</listitem>
</itemizedlist>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Handling Security Exceptions</title>
<para>
@@ -377,9 +377,9 @@
Seam includes some special functionality for handling this problem.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Login Redirection</title>
<para>
@@ -422,9 +422,9 @@
the conversation in your <literal>authenticate()</literal> method.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>HTTP Authentication</title>
<para>
@@ -452,7 +452,7 @@
authentication realm that is presented to the user when they authenticate.
</para>
- <sect3>
+ <section>
<title>Writing a Digest Authenticator</title>
<para>
@@ -480,11 +480,11 @@
}
}
]]></programlisting>
- </sect3>
+ </section>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Advanced Authentication Features</title>
<para>
@@ -492,7 +492,7 @@
security requirements.
</para>
- <sect3>
+ <section>
<title>Using your container's JAAS configuration</title>
<para>
@@ -510,13 +510,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>
@@ -599,9 +599,9 @@
</tbody>
</tgroup>
</table>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Authorization</title>
<para>
@@ -612,7 +612,7 @@
above.
</para>
- <sect2>
+ <section>
<title>Core concepts</title>
<para>
@@ -630,9 +630,9 @@
for example <literal>customer:delete</literal>, or <literal>customer:insert</literal>.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Securing components</title>
<para>
@@ -640,7 +640,7 @@
<literal>@Restrict</literal> annotation.
</para>
- <sect3>
+ <section>
<title>The @Restrict annotation</title>
<para>
@@ -720,9 +720,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
@@ -764,10 +764,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>
@@ -828,9 +828,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
@@ -861,9 +861,9 @@
<literal>admin</literal> role.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Securing Entities</title>
<para>
@@ -992,7 +992,7 @@
your JPA provider.
</para>
- <sect3>
+ <section>
<title>Entity security with JPA</title>
<para>
@@ -1016,9 +1016,9 @@
</entity-mappings>]]></programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Entity security with a Managed Hibernate Session</title>
<para>
@@ -1027,13 +1027,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>
@@ -1042,7 +1042,7 @@
checks are processed, and how to implement permission checks for a Seam application.
</para>
- <sect2>
+ <section>
<title>Permissions Overview</title>
<para>
@@ -1053,9 +1053,9 @@
algorithms for evaluating large numbers of complex rules involving multiple conditions.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Configuring a rules file</title>
<para>
@@ -1085,9 +1085,9 @@
<para>
Once the <literal>RuleBase</literal> component is configured, it's time to write the security rules.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Creating a security rules file</title>
<para>
For this step you need to create a file called <literal>security.drl</literal> in the
@@ -1217,7 +1217,7 @@
intended for.
</para>
- <sect3>
+ <section>
<title>Wildcard permission checks</title>
<para>
@@ -1239,13 +1239,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>
@@ -1301,9 +1301,9 @@
sensitive data from pages using HTTPS to other pages using HTTP.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>CAPTCHA</title>
<para>
@@ -1313,7 +1313,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
@@ -1330,9 +1330,9 @@
<url-pattern>/seam/resource/*</url-pattern>
</servlet-mapping>]]></programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Adding a CAPTCHA to a form</title>
<para>
@@ -1351,9 +1351,9 @@
validated against the CAPTCHA when the form is submitted.
</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Customising the CAPTCHA algorithm</title>
<para>
@@ -1380,11 +1380,11 @@
}
}]]></programlisting>
- </sect2>
+ </section>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Security Events</title>
<para>
@@ -1536,9 +1536,9 @@
</tgroup>
</table>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Run As</title>
<para>
@@ -1575,9 +1575,9 @@
<literal>RunAsOperation</literal>.
</para>
- </sect1>
+ </section>
- <sect1>
+ <section>
<title>Extending the Identity component</title>
<para>
@@ -1623,6 +1623,6 @@
}
}]]></programlisting>
- </sect1>
+ </section>
</chapter>
Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Webservices.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Webservices.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Webservices.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -11,7 +11,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,
@@ -44,9 +44,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
@@ -93,7 +93,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>
@@ -116,11 +116,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>
@@ -200,7 +200,7 @@
and delegating the real work to a conversational Seam component.
</para>
- </sect1>
+ </section>
</chapter>
Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Xml.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Xml.xml 2009-12-04 07:49:23 UTC (rev 11723)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Xml.xml 2009-12-04 07:54:45 UTC (rev 11724)
@@ -14,7 +14,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,
@@ -35,9 +35,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>
@@ -244,9 +244,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
@@ -285,9 +285,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:
@@ -350,9 +350,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
@@ -539,7 +539,7 @@
</itemizedlist>
- </sect1>
+ </section>
</chapter>
More information about the seam-commits
mailing list