Hello,
Well, I thought I share a little I do not used the same configuration as you but I will try to show you As I understand:
When deploying ejb weblogic on a server, you can also generate customers who can call in the ejb remote. It is also valid for other server applications.
Here are the config files generated by weblogic for a call to a ejb given:
ejb-jar.xml:
Code:
<session>
<ejb-name> MyBeanSession </ ejb-name>
<home> en.edf.erdsge.ejb.mybean.MyBeanSessionHome </ home>
<remote> en.edf.erdsge.ejb.mybean.MyBeanSessionRemote </ remote>
<local-home> en.edf.erdsge.ejb.mybean.MyBeanSessionLocalHome </ local-home>
<local> en.edf.erdsge.ejb.mybean.MyBeanSessionLocal </ local>
<ejb-class> en.edf.erdsge.ejb.mybean.MyBeanSession </ ejb-class>
Stateless <session-type> </ session-type>
<transaction-type> Container </ transaction-type>
</ session>
weblogic-ejb-jar.xml:
Code:
<weblogic-enterprise-bean>
<ejb-name> MyBeanSession </ ejb-name>
<stateless-session-descriptor>
</ stateless-session-descriptor>
<enable-call-by-reference> true </ enable-call-by-reference>
<jndi-name> ejb.MyBeanSessionRemoteHome </ jndi-name>
<local-jndi-name> ejb.MyBeanSessionLocalHome </ local-jndi-name>
</ weblogic-enterprise-bean>
Here the lookup jndi fetches the reference in jndi weblogic-ejb-jar.xml then goes to the mapping in ejb-jar.xml to retrieve the name of the ejb to load classes that go well. These classes * * local and remote are delivered to the customer.
I hope it can help you
Good luck,
Bookmarks