Correction: this is only for EJBs that are accessed by Seam by annotating
them with Seam's @Name.
digi_pixel wrote:
>
> Yes in fact I was under the advise that session EJBs had to be registered
> in web.xml when the EAR was being deployed to Glassfish since Seam is
> completely unable to determine how to access the EJB from the container.
> There is no issue with this if the EAR is deployed to JBoss instead.
>
>
>
> Jason Lee wrote:
>>
>> Oh, ok. Are you trying to expose an EJB as a Seam component?
>>
>> --
>> Jason Lee, SCJP
>> Software Architect -- Objectstream, Inc.
>> Mojarra and Mojarra Scales Dev Team
>> https://mojarra.dev.java.net
>> https://scales.dev.java.net
>> http://blogs.steeplesoft.com
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Seam-Support-In-Glassfish-tp14934510p14944713.html
Sent from the java.net - glassfish users mailing list archive at Nabble.com.