Calling EJBs across ears - HomeObject not found

Question

I have this situation:
- BeanA is a stateless session bean and packaged in mod1.ear. mod1.ear also has
a jar file which contains BeanB's home and remote interface. In mod1.ear's application.xml,
I have mentioned the BeanA's jar and BeanB's client jar containing only the home
and remote interfaces of BeanB. BeanB's client jar is marked as a java module
in mod1.ear's application.xml file.
- BeanB is also a stateless session bean and packaged in mod2.ear.
- BeanA does a lookup for BeanB and then calls a business method of BeanB.
The issue:
- When BeanA does a lookup, I get an exception saying BeanBHome is not found.
Basically I think it is an issue with the classloader. BeanA is not getting BeanB's
home. I did a hack by adding BeanB's client jar in the classpath of startServer.cmd.
It works, but I think it is not a clean way.
Can someone let me know what the right solution is?
Thanks,
Abbas

Answer 1

Hello Abbas,
Please provide your manifest classpath entries and any other files/information
that may be necessary to detect the problem. Also, for more information about
WebLogic classoading mechanisms, if you haven't done so please read http://dev2dev.bea.com/articles/musser.jsp.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Abbas" <[email protected]> wrote:
>
Rob:
I included the BeanB's ejb-client.jar entry in the manifest file of BeanA's
ejb-jar.
However, it doesn't work. I think Weblogic should load BeanA's jar and
BeanB's
ejb-client jar with the same classloader. I couldn't figure out why BeanA
couldn't
locate the home interface. If I copy the BeanB's class files into BeanA's
jar,
obviously it works. But that wouldn't be a clean way to work.
I have replicated the scenario with 2 sample beans. I can upload them
if you or
someone can let me know if I am missing something.
Thanks,
Abbas
Rob Woollen <[email protected]> wrote:
Abbas wrote:
I have this situation:
- BeanA is a stateless session bean and packaged in mod1.ear. mod1.earalso has
a jar file which contains BeanB's home and remote interface. In mod1.ear'sapplication.xml,
I have mentioned the BeanA's jar and BeanB's client jar containingonly the home
and remote interfaces of BeanB.Ok
BeanB's client jar is marked as a java module
in mod1.ear's application.xml file.No, remove that.
In beanA's ejb-jar file add a manifest class-path entry that references
beanB's ejb-client-jar.
-- Rob
- BeanB is also a stateless session bean and packaged in mod2.ear.
- BeanA does a lookup for BeanB and then calls a business method ofBeanB.
The issue:
- When BeanA does a lookup, I get an exception saying BeanBHome isnot found.
Basically I think it is an issue with the classloader. BeanA is notgetting BeanB's
home. I did a hack by adding BeanB's client jar in the classpath ofstartServer.cmd.
It works, but I think it is not a clean way.
Can someone let me know what the right solution is?
Thanks,
Abbas