Client JNDI support for AS7

The following use case are applicable both to a remote/client VM and within AS7 itself.

The configuration of the initial context is not specified in here, it'll be a resultant of this task and outlined in some documentation.

Note that any

InitialContext ctx = new InitialContext();

might need

InitialContext ctx = new InitialContext(props);

where the actual contents of props is currently unspecified.

Calling AS7

It must be possible for a client to call AS7 via the following code:

InitialContext ctx = new InitialContext();
MyRemote bean = ctx.lookup("java:myserver1/myapp/myjar/myBean#MyRemote");

Calling different AS7 instances

It should be possible for a client to call two different AS7 instances via the following code:

InitialContext ctx = new InitialContext();
MyRemote bean = ctx.lookup("java:myserver1/myapp/myJar/OtherBean#MyRemote");
OtherRemote bean2 = ctx.lookup("java:myserver2/otherapp/otherjar/OtherBean2#OtherRemote");

Whether security and transaction propagation between the servers is available or possible is left beyond scope.

Calling different type/version of servers

It may be possible for a client to call two different EAP versions via the following code:

InitialContext ctx = new InitialContext();
MyRemote bean = ctx.lookup("java:myEAP6/myapp/myJar/OtherBean#MyRemote");
OtherRemote bean2 = ctx.lookup("java:myEAP5/otherapp/otherjar/OtherBean2#OtherRemote");

The last one would require a context to be associated with a certain module to load the proper client classes. See also http://wolf-71.blogspot.com/2010/02/et-phone-home.html

Whether security and transaction propagation between the servers is available or possible is left beyond scope. Also the propagation of the current established tx/sec context might not be available.