On Thu, 27 Jun 2002, Sacha Labourey wrote:

> > Yes. But if we need to bootsrap the jndi communication, we can skip this
> > jndi lookup and just send the create invocation to the invoker. How the
> > invokers can be accessed must either be "wellknown" or somehow configured
> > on the client.
> 
> yes, the problem is that I am not sure (in fact I am pretty sure that it is
> not possible with RMI/JRMP) that it is possible to have "well-known" ports
> for a very simply reason: SocketFactory can be set for the RMI invoker on
> the server side for example. If I remember well, this well-known thing is
> possible  with CORBA.
> 
> > Please, please tell me, for what do we need server side jndi content on
> > the client?
> 
> ?!? MyHome home = ctx.lookup (MyHome.JNDI_NAME); ?!?
> 
> Do I understand your question?
> 

That is local jndi. I am looking up the "coded name" in my local 
jndi-namespace. The coded name is defined as an ejb-ref in my 
application-client.xml. what I get is something, that feels like a proxy 
to the ejb's home. the ejb-ref must be configured with:

o an url, that points to the invoker (protocol, server, "context")
o the jndi-name of the bean
o optional client interceptors

if I invoke create(..) on this proxy, the invocation is stuffed with the 
jndi-name and forwarded to the invoker (url). the invoker returns a 
handle, that contains all configuration, that is required to setup the 
invoker proxy and the client interceptors.

So now tell me, for what do I need the server side jndi content on the 
client? Maybe, I'm missing something ..

connecting to a cluster might need some more configuration (there are more 
than one servers/invokers). but it's not harder to connect to a clustered 
invoker than to bootstrap clustered jndi access.

restriction: all home methods (create, finders, entity) won't have the 
interceptor configuration from the server.

Holger



-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to