[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Sat Feb 10 11:42:48 EST 2007
User: gavin
Date: 07/02/10 11:42:48
Modified: doc/reference/en/modules configuration.xml
conversations.xml events.xml
Log:
more updates
Revision Changes Path
1.37 +44 -2 jboss-seam/doc/reference/en/modules/configuration.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: configuration.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/configuration.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -b -r1.36 -r1.37
--- configuration.xml 10 Feb 2007 16:31:59 -0000 1.36
+++ configuration.xml 10 Feb 2007 16:42:48 -0000 1.37
@@ -251,6 +251,13 @@
<sect3>
<title>Context filter</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 access to Seam
+ components.
+ </para>
+
+ <para>
This filter allows custom servlets to interact with the Seam contexts. It
sets up the Seam contexts at the beginning of each request, and tears
them down at the end of the request. You should make sure that this filter
@@ -263,8 +270,7 @@
<literal>components.xml</literal> to enable it:
</para>
- <programlisting><![CDATA[<web:context-filter installed="true"
- url-pattern="/custom/*"/>]]></programlisting>
+ <programlisting><![CDATA[<web:context-filter url-pattern="/media/*"/>]]></programlisting>
<itemizedlist>
<listitem>
@@ -276,6 +282,19 @@
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ The context filter expects to find the conversation id of any
+ conversation context in a request parameter named <literal>conversationId</literal>.
+ You are responsible for ensuring that it gets sent in the request.
+ </para>
+
+ <para>
+ You are also responsible for ensuring propagation of any new conversation id back
+ to the client. Seam exposes the conversation id as a property of the built in
+ component <literal>conversation</literal>.
+ </para>
+
</sect3>
</sect2>
@@ -1073,4 +1092,27 @@
</sect1>
+ <sect1>
+ <title>Seam and 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 servlet that needs access to Seam components.
+ </para>
+ <para>
+ This servlet filter is responsible for initializing all Seam contexts before
+ passing control to the servlet. It expects to find the conversation id of any
+ conversation context in a request parameter named <literal>conversationId</literal>.
+ You are responsible for ensuring that it gets sent in the request.
+ </para>
+
+ <para>
+ You are also responsible for ensuring propagation of any new conversation id back
+ to the client. Seam exposes the conversation id as a property of the built in
+ component <literal>conversation</literal>.
+ </para>
+
+ </sect1>
+
</chapter>
\ No newline at end of file
1.24 +0 -48 jboss-seam/doc/reference/en/modules/conversations.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: conversations.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/conversations.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- conversations.xml 28 Jan 2007 05:49:56 -0000 1.23
+++ conversations.xml 10 Feb 2007 16:42:48 -0000 1.24
@@ -813,52 +813,4 @@
</section>
- <section>
- <title>Seam and 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 servlet that needs access to Seam components.
- </para>
-
- <programlisting><![CDATA[<filter>
- <filter-name>Seam Servlet Filter</filter-name>
- <filter-class>org.jboss.seam.servlet.SeamServletFilter</filter-class>
-</filter>
-
-<filter-mapping>
- <filter-name>Seam Servlet Filter</filter-name>
- <url-pattern>*.ajax</url-pattern>
-</filter-mapping>]]></programlisting>
-
- <para>
- This servlet filter is responsible for initializing all Seam contexts before
- passing control to the servlet. It expects to find the conversation id of any
- conversation context in a request parameter named <literal>conversationId</literal>.
- You are responsible for ensuring that it gets sent in the request.
- </para>
-
- <para>
- You are also responsible for ensuring propagation of any new conversation id back
- to the client. Seam exposes the conversation id as a property of the built in
- component <literal>conversation</literal>.
- </para>
-
- <para>
- Seam also provides the Seam Remoting framework, a simple way to expose any method
- of a Seam component for invocation by an asynchronous JavaScript request simply
- by annotating the methods that should be accessible in the client. See the Seam
- Remoting chapter for further information.
- </para>
-
- </section>
-
- <section>
- <title>Seam and SOAP</title>
-
- <para>TODO</para>
-
- </section>
-
</chapter>
\ No newline at end of file
1.13 +5 -5 jboss-seam/doc/reference/en/modules/events.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: events.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/events.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- events.xml 5 Feb 2007 06:03:46 -0000 1.12
+++ events.xml 10 Feb 2007 16:42:48 -0000 1.13
@@ -748,17 +748,17 @@
<title>Enabling Seam exception handling</title>
<para>
- To enable Seam's exception handling, we need to add a servlet filter to
- <literal>web.xml</literal>:
+ To enable Seam's exception handling, we need to make sure we have the master servlet
+ filter declared in <literal>web.xml</literal>:
</para>
<programlisting><![CDATA[<filter>
- <filter-name>Seam Exception Filter</filter-name>
- <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
+ <filter-name>Seam Filter</filter-name>
+ <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
</filter>
<filter-mapping>
- <filter-name>Seam Exception Filter</filter-name>
+ <filter-name>Seam Filter</filter-name>
<url-pattern>*.seam</url-pattern>
</filter-mapping>]]></programlisting>
More information about the jboss-cvs-commits
mailing list