When you say Session and Entity locator are these global
objects implementing the ServiceLocator pattern? 
Are you caching the java:comp/env context globally?
This context changes depending on where you look it up. If you
cache it globally, it is likely you are using a different
bean's ENC (whichever was the first to look it up).

Regards,
Adrian

On Sat, 2003-08-30 at 05:35, Matthew Hixson wrote:
> On Friday, August 29, 2003, at 08:31  PM, Adrian Brock wrote:
> 
> > I didn't spot web.xml on the first pass.
> >
> > Is your war in an ear with the ejb? ejb-link will only
> > work in the same deployment unit.
> 
> I have an ear that contains an application.xml with:
> 
> <application>
>     <display-name>Versaly</display-name>
>     <description>Versaly</description>
>     <module>
>        <ejb>versaly.jar</ejb>
>     </module>
>     <module>
>        <web>
>           <web-uri>versaly.war</web-uri>
>           <context-root>/</context-root>
>        </web>
>     </module>
> </application>
> 
> The only place I have a web.xml is within versaly.war.  What I can't 
> figure out is why the session locator can find the PartnerServices 
> session bean, but the entity locator cannot find the Content entity 
> bean.  Both locator classes are called from within the .war file and 
> all EJBs are declared in the .jar file in its ejb-jar.xml.
>    Thanks,
>      -M@
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to