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

[Dan Allen]

Ah, that was me. It was true at the time I wrote it, which paralleled those
discussions. But I know from my own tests that the references are no longer
needed in JBoss AS 5. I'll update it.

-Dan

On Sun, Mar 15, 2009 at 6:40 PM, Pete Muir <pmuir at redhat.com> wrote:

> Guys,
>
> whoever wrote this, please note it's not true - I went through many
> discussions with the JBoss AS/EJB3 team to make sure this feature from JBoss
> 4 was preserved
>
> Thanks
>
> Begin forwarded message:
>
>  From: seam-commits at lists.jboss.org
>> Date: 15 March 2009 22:33:07 GMT
>> To: seam-commits at lists.jboss.org
>> Subject: [seam-commits] Seam SVN: r10166 -
>> trunk/doc/Seam_Reference_Guide/en-US.
>> Reply-To: seam-commits at lists.jboss.org
>>
>> Author: pete.muir at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-commits
>>
>
> --
> Pete Muir
> http://www.seamframework.org
> http://in.relation.to/Bloggers/Pete
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>



-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20090315/9dcba995/attachment.html