From: Eric K. <eri...@ar...> - 2002-05-02 20:39:44
|
I seem to be caught in a catch-22, or something like it. I have two ejb jars. Jar A has ejbs which reference those in Jar B. Both Jars are then built into an ear file. In the ejb-jar.xml for jar A, the ejb-ref statements do not have ejb-link elements for the ejbs in jar b, since they are not in the same jar. I put jndi-name elements in the jboss.xml for jar b corresponding to the ejb-ref elements in jar A. When I deploy, I get the message could not deploy file...expected either ejb-link in ejb-jar.xml or jndi-name in jboss.xml. Two questions: 1. Is putting the jndi-name elements in jboss.xml in jar b correct? 2. Do I need to put the jndi-name elements in a jboss.xml at all for these references? My client has NO problem finding the beans on the server. I understand the need for flexibility using jndi, but in 98% of the instances the flexibility is not needed (my bean is called ejb/bean and i don't need two levels of indirection). What's the right thing to do here? I'd include the various xml files but they're pretty long. I can fix this apparently by putting the link elements in jar a, but that's not correct since the references are in jar b... thanks Eric Kaplan Armanta, Inc. 55 Madison Ave. Morristown, NJ 07960 Phone: (973) 326-9600 |