[webbeans-commits] Webbeans SVN: r3667 - doc/trunk/reference/en-US.
webbeans-commits at lists.jboss.org
webbeans-commits at lists.jboss.org
Tue Sep 15 09:02:01 EDT 2009
Author: pete.muir at jboss.org
Date: 2009-09-15 09:02:01 -0400 (Tue, 15 Sep 2009)
New Revision: 3667
Modified:
doc/trunk/reference/en-US/ri-spi.xml
Log:
add notes on new JSF/JSP integration
Modified: doc/trunk/reference/en-US/ri-spi.xml
===================================================================
--- doc/trunk/reference/en-US/ri-spi.xml 2009-09-15 13:00:42 UTC (rev 3666)
+++ doc/trunk/reference/en-US/ri-spi.xml 2009-09-15 13:02:01 UTC (rev 3667)
@@ -579,7 +579,7 @@
<listitem>
<para>
- If you are integrating the Web Beans into a JSF
+ If you are integrating the Web Beans into a JSF
environment you must register
<literal>org.jboss.webbeans.jsf.WebBeansPhaseListener</literal>
as a phase listener.
@@ -588,12 +588,41 @@
<para>
If you are integrating the Web Beans into a JSF
environment you must register
- <literal>org.jboss.webbeans.jsf.WebBeansApplicationFactory</literal>
- as an (wrapping) factory for the <literal>Application</literal>.
+ <literal>org.jboss.webbeans.el.WebBeansELContextListener</literal>
+ as as an EL Context listener.
</para>
<para>
If you are integrating the Web Beans into a JSF environment
+ you must obtain the bean manager for the module and then call
+ <literal>BeanManager.wrapExpressionFactory()</literal>,
+ passing <literal>Application.getExpressionFactory()</literal>
+ as the argument. The wrapped expression factory must be used
+ in all EL expression evaluations performed by JSF in this web
+ application.
+ </para>
+
+ <para>
+ If you are integrating the Web Beans into a JSF environment
+ you must obtain the bean manager for the module and then call
+ <literal>BeanManager.getELResolver()</literal>,
+ The returned EL resolver should be registered with JSF for
+ this web application.
+ </para>
+
+ <tip>
+ <para>
+ There are a number of ways you can obtain the bean manager
+ for the module. You could call
+ <literal>Bootstrap.getManager()</literal>, passing in the
+ BDA for this module. Alternatively, you could use the
+ injection into Java EE component classes, or look up the
+ bean manager in JNDI.
+ </para>
+ </tip>
+
+ <para>
+ If you are integrating the Web Beans into a JSF environment
you must register
<literal>org.jboss.webbeans.servlet.ConversationPropagationFilter</literal>
as a Servlet listener, either automatically, or through user
@@ -611,6 +640,49 @@
</varlistentry>
<varlistentry>
<term>
+ JSP
+ </term>
+ <listitem>
+
+ <para>
+ If you are integrating the Web Beans into a JSP
+ environment you must register
+ <literal>org.jboss.webbeans.el.WebBeansELContextListener</literal>
+ as as an EL Context listener.
+ </para>
+
+ <para>
+ If you are integrating the Web Beans into a JSP environment
+ you must obtain the bean manager for the module and then call
+ <literal>BeanManager.wrapExpressionFactory()</literal>,
+ passing <literal>Application.getExpressionFactory()</literal>
+ as the argument. The wrapped expression factory must be used
+ in all EL expression evaluations performed by JSP.
+ </para>
+
+ <para>
+ If you are integrating the Web Beans into a JSP environment
+ you must obtain the bean manager for the module and then call
+ <literal>BeanManager.getELResolver()</literal>,
+ The returned EL resolver should be registered with JSP for
+ this web application.
+ </para>
+
+ <tip>
+ <para>
+ There are a number of ways you can obtain the bean manager
+ for the module. You could call
+ <literal>Bootstrap.getManager()</literal>, passing in the
+ BDA for this module. Alternatively, you could use the
+ injection into Java EE component classes, or look up the
+ bean manager in JNDI.
+ </para>
+ </tip>
+
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>
Session Bean Interceptor
</term>
<listitem>
More information about the weld-commits
mailing list