Eric Kaplan wrote: > while we're on the subject of naming, i remember a while ago when i first > started with jboss that clients looked up beans differently than other beans > on the app server. This was highlighted specifically in the documentation > on the web. > > client - "ejb/foo"
This is true if you didn't put an ejb-ref stanza in your web.xml, and if you specified ejb/foo as the bean's JNDI name in jboss.xml. The ejb-ref stanza in web.xml follows the same rules as in ejb-jar.xml: it can have either have a link in it if your bean is in the same ear or you can specify a mapping in jboss-web.xml. The bottom line is that your web client code should look up the ejb the same way that ejbs look up ejbs. If your client is a stand-alone client, on the other hand, the it has to look up the ejb by the ejb's JNDI name as specified in jboss.xml. The default for this is simply the bean name as specified in ejb-jar.xml. Since the JNDI name that an ejb is deployed to is container dependent, this is not totally portable. One way to help portability in this case is to put the bean JNDI names into a property file, so that at least you don't have to change code to go to a different naming scheme. Note that the J2EE client application spec addresses portability in this area, but that JBoss doesn't support J2EE client applications, onlly standalone client applications. danch _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
