On Thu, 27 Jun 2002, Holger Engels wrote: > 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.
Ok, I can see it now. Fetching the complete invoker proxy from the server is the better idea. It works also with other component types (without home interfaces). Still want the mapping from coded names to jndi-names in my application-client.xml and still want to have the possibility to specify additional interceptors for *-refs. Holger ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
