[seam-commits] Seam SVN: r9660 - trunk/doc/Seam_Reference_Guide/en-US.

[seam-commits at lists.jboss.org]

Author: dan.j.allen
Date: 2008-11-26 03:06:45 -0500 (Wed, 26 Nov 2008)
New Revision: 9660

Modified:
   trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml
Log:
JBSEAM-3034 - additional notes


Modified: trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml
===================================================================
--- trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml	2008-11-26 07:57:13 UTC (rev 9659)
+++ trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml	2008-11-26 08:06:45 UTC (rev 9660)
@@ -489,9 +489,10 @@
 ]]></programlisting>
 
             <para> Assuming your EJB bean class is deployed in an EAR named myapp, the global JNDI name 
-                myapp/AuthenticatorBean/local will be assigned to it. As you learned, you can reference this EJB
-                component as a Seam component with the name <literal>authenticator</literal> and Seam will take care of
-                finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation). </para>
+                myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. As you learned, you can reference this
+                EJB component as a Seam component with the name <literal>authenticator</literal> and Seam will take care
+                of finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation).
+                </para>
 
             <para> So what about the rest of the application servers? Well, according to the Java EE spec, which most
                 vendors try to adhere to religiously, you have to declare an EJB reference for your EJB in order for it
@@ -499,10 +500,10 @@
                 JNDI naming convention so that you can leverage the Seam JNDI pattern. You might find the JBoss
                 convention a good one to follow.</para>
 
-            <para> There are two places you have to define the EJB reference. If you are going to be looking up the
-                Seam EJB component through JSF (in a JSF view or as a JSF action listener) or a Seam JavaBean component,
-                then you must declare the EJB reference in web.xml. Here is the EJB reference for the example component
-                just shown: </para>
+            <para> There are two places you have to define the EJB reference when using Seam on non-JBoss application
+                servers. If you are going to be looking up the Seam EJB component through JSF (in a JSF view or as a JSF
+                action listener) or a Seam JavaBean component, then you must declare the EJB reference in web.xml. Here
+                is the EJB reference for the example component just shown: </para>
 
             <programlisting role="XML"><![CDATA[<ejb-local-ref>
     <ejb-ref-name>myapp/AuthenticatorBean/local</ejb-ref-name>
@@ -521,7 +522,8 @@
                 <literal>@In</literal>, it isn't going to be successful looking up the component in JNDI. You cannot
                 simply resolve JNDI names as you please. You have to define those references explicitly. Unlike with the
                 web context, however, you cannot declare EJB references globally for all EJB components. Instead, you
-                have to specify the JNDI resources for a given EJB component one-by-one.</para>
+                have to specify the JNDI resources for a given EJB component one-by-one (this applies to JBoss AS 5 in
+                addition to non-JBoss application servers).</para>
 
             <para> Let's assume that we have an EJB named RegisterAction (the name is resolved using the three steps
                 mentioned previously). That EJB has the following Seam injection:</para>