Author: peteroyle Date: 2009-10-02 06:43:12 -0400 (Fri, 02 Oct 2009) New Revision: 3834 Modified: doc/trunk/reference/en-US/environments.xml Log: Updated documentation to reflect API changes Modified: doc/trunk/reference/en-US/environments.xml =================================================================== --- doc/trunk/reference/en-US/environments.xml 2009-10-02 09:33:39 UTC (rev 3833) +++ doc/trunk/reference/en-US/environments.xml 2009-10-02 10:43:12 UTC (rev 3834) @@ -257,16 +257,11 @@ </listitem> <listitem> <para> - <literal>Binding Types</literal> + <literal>Qualifiers</literal> </para> </listitem> <listitem> <para> - <literal>Deployment Types</literal> - </para> - </listitem> - <listitem> - <para> <literal>Stereotypes</literal> </para> </listitem> @@ -282,11 +277,11 @@ <para>To make life easy for developers Web Beans provides a special module with a main method which will boot the Web Beans manager, - automatically registering all simple Web Beans found on the classpath. + automatically registering all simple beans found on the classpath. This eliminates the need for application developers to write any bootstrapping code. The entry point for a Web Beans SE applications - is a simple Web Bean which observes the standard <literal>@Deployed - Manager</literal> event. The command line paramters can be + is a simple Web Bean which observes the special <literal>ContainerInitialized</literal> + event provided by the SE module. The command line paramters can be injected using either of the following: </para> <programlisting role="JAVA"><![CDATA[@Parameters List<String> params; @@ -300,7 +295,7 @@ { @Parameters List<String> parameters; - public void printHello( @Observes @Deployed Manager manager ) + public void printHello( @Observes ContainerInitialized event ) { System.out.println( "Hello " + parameters.get(0) ); } @@ -312,24 +307,25 @@ <para>If you need to do any custom initialization of the Web Beans manager, for example registering custom contexts or initializing resources for - your beans you can do so in response to the <literal>@Initialized Manager</literal> - event. The following example registers a custom context:</para> + your beans you can do so in response to the <literal>AfterBeanDiscovery</literal> + or <literal>AfterDeploymentValidation</literal> + events. The following example registers a custom context:</para> <programlisting role="JAVA"><![CDATA[public class PerformSetup { - public void setup( @Observes @Initialized Manager manager ) + public void setup( @Observes AfterBeanDiscovery event ) { - manager.addContext( ThreadContext.INSTANCE ); + event.addContext( ThreadContext.INSTANCE ); } }]]></programlisting> <note> <para> The command line parameters do not become available for injection - until the <literal>@Deployed Manager</literal> event is fired. If you + until the <literal>ContainerInitialized</literal> event is fired. If you need access to the parameters during initialization you can do so via the - <literal>public static String getParameters()</literal> method in + <literal>public static String[] getParameters()</literal> method in <literal>StartMain</literal>. </para> </note>