[seam-dev] Fwd: [seam-commits] Seam SVN: r10166 - trunk/doc/Seam_Reference_Guide/en-US.

From: seam-commits(a)lists.jboss.org Date: 15 March 2009 22:33:07 GMT To: seam-commits(a)lists.jboss.org Subject: [seam-commits] Seam SVN: r10166 - trunk/doc/ Seam_Reference_Guide/en-US. Reply-To: seam-commits(a)lists.jboss.org Author: pete.muir(a)jboss.org Date: 2009-03-15 18:33:05 -0400 (Sun, 15 Mar 2009) New Revision: 10166 Modified: trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml Log: Fix nonsense in docs! Modified: trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml =================================================================== --- trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml 2009-03-14 07:34:37 UTC (rev 10165) +++ trunk/doc/Seam_Reference_Guide/en-US/Configuration.xml 2009-03-15 22:33:05 UTC (rev 10166) @@ -522,8 +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 (this applies to JBoss AS 5 in - addition to non-JBoss application servers).</para> + have to specify the JNDI resources for a given EJB component one-by-one (this only applies to + non-JBoss application servers of course!).</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> _______________________________________________ seam-commits mailing list seam-commits(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-commits