From webbeans-commits at lists.jboss.org Thu Apr 23 18:55:19 2009 Content-Type: multipart/mixed; boundary="===============0596029630849494380==" MIME-Version: 1.0 From: webbeans-commits at lists.jboss.org To: weld-commits at lists.jboss.org Subject: [webbeans-commits] Webbeans SVN: r2616 - doc/trunk/reference/en-US. Date: Thu, 23 Apr 2009 18:50:50 -0400 Message-ID: --===============0596029630849494380== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: dan.j.allen Date: 2009-04-23 18:50:49 -0400 (Thu, 23 Apr 2009) New Revision: 2616 Modified: doc/trunk/reference/en-US/environments.xml Log: WBX-31 Modified: doc/trunk/reference/en-US/environments.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- doc/trunk/reference/en-US/environments.xml 2009-04-22 18:42:57 UTC (rev= 2615) +++ doc/trunk/reference/en-US/environments.xml 2009-04-23 22:50:49 UTC (rev= 2616) @@ -45,7 +45,7 @@ =
- Glassfish + GlassFish = TODO
@@ -65,11 +65,11 @@ = - Web Beans should be used as a web application library in a servle= t = - container. You should place webbeans-servlet.jar in - WEB-INF/lib. webbeans-serv;et.jar - is an "uber-jar" provided for your convenience. Instead, you coul= d use - its component jars: = + Web Beans should be used as a web application library in a servlet + container. You should place webbeans-servlet.jar + in WEB-INF/lib. + webbeans-servlet.jar is an "uber-jar" provided= for + your convenience. Alternatively, you could use its component jars= : = = @@ -117,41 +117,43 @@ = You also need to explicitly specify the servlet listener (used to - boot Web Beans, and control its interaction with requests) in = + boot Web Beans, and control its interaction with requests) in web.xml: = - + org.jboss.webbeans.environment.servlet.Listener ]]> =
Tomcat = - - Tomcat has a read-only JNDI, so Web Beans can't automatically bi= nd = - the Manager. To bind the Manager into JNDI, you should add the = - following to your META-INF/context.xml: - + + Tomcat has a read-only JNDI, so Web Beans can't automatically = bind = + the Manager. To bind the Manager into JNDI, you should populat= e = + META-INF/context.xml with the following + contents: + = - -]]> + + +]]> = - and make it available to your deployment by adding this to = - web.xml: + and make it available to your deployment by adding this to = + the bottom of web.xml: = - - - app/Manager - - - javax.inject.manager.Manager - + + + app/Manager + + + javax.inject.manager.Manager + ]]> = @@ -163,14 +165,59 @@ Web Beans also supports Servlet injection in Tomcat. To enable= this, place the webbeans-tomcat-support.jar in = - $TOMCAT_HOME/lib, and add the following to y= our - META-INF/context.xml: + $TOMCAT_HOME/lib, and add the following to = your + META-INF/context.xml: = - ]]> + ]]> =
= +
+ Jetty + + + Like Tomcat, Jetty has a read-only JNDI, so Web Beans can't + automatically bind the Manager. To bind the Manager to JNDI, y= ou + should populate WEB-INF/jetty-env.xml with = the + following contents: + + = + + + + = + app/Manager + + + javax.inject.manager.Manager = + org.jboss.webbeans.resources.ManagerObjectFactory + + + + +]]> + + + Notice that Jetty doesn't not have built-in support for an + javax.naming.spi.ObjectFactory like Tomcat,= so + it's necessary to manually create the + javax.naming.Reference to wrap around it. + + + + Jetty only allows you to bind entries to + java:comp/env, so the Manager will be avail= able = + at java:comp/env/app/Manager + + + + Web Beans does not currently support Servlet injection in Jett= y. + + +
+ =
@@ -286,4 +333,4 @@ =
= - \ No newline at end of file + --===============0596029630849494380==--