JBossDeveloper

Just wondering, the document about JNDI in AS 7 states the following:

For example, an EJB receiver "Foo" might be able to handle invocation on a bean identified by app-A/module-A/distinctinctName-A/Bar!RemoteBar, whereas a EJB receiver named "Blah" might be able to handle invocation on a bean identified by app-B/module-B/distinctName-B/BeanB!RemoteBean. Each such EJB receiver knows about what set of EJBs it can handle

This isn't explained further. How does each such EJB receiver knows about this set? Does it query each configured server once to retrieve a kind of index or directory with available remote beans?

arjan tijms wrote:

 

This isn't explained further. How does each such EJB receiver knows about this set? Does it query each configured server once to retrieve a kind of index or directory with available remote beans?

I left that out of the JNDI chapter and am going to include it in the EJB client API documentation which explains all this. In short, whenever the client API makes a connection with the remote server, we send back the EJB deployment related information on that server as part of the protocol messages. The client will thus know what that server is capable of handling.

Hello Jaikiran,

the Java EE 6 Spec. states:

Application clients are first tier client programs that execute in their own Java™ virtual machines. (EE.10.1)

As with all Java EE components, application clients use JNDI to look up enterprise beans, get access to resource managers, reference configurable parameters set at deployment time, and so on. Application clients use the java: JNDI namespace to access these items. (EE.10.4)

AS7 does have support for "application clients". You'll have to start the application client container for that (the script is JBOSS_HOME/bin/appclient.sh).