geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [jsr109] geronimo integration
Date Wed, 03 Dec 2003 13:15:35 GMT
The JNDI Binding, it's to accomplish the client model of the JSR-109 (page
55) spec. This sepecified that the ws-references declared in the DD's must
be resolved generating client classes (stubs, proxys or DI) that implements
the service interface and this classes must be binded on JNDI.

In this case, the geronimo classes will giove the DD's to the JSR-109 impl
and this will return the set of classes that implements the service interface
and the Port client, and geronimo classes will bind them to JNDI.


>-- Original Message --
>Date: Tue, 02 Dec 2003 22:09:23 -0800
>From: Jeremy Boynes <>
>Subject: Re: [jsr109] geronimo integration
>Dain Sundstrom wrote:
>> I have one clarifying question.  What is the role of the JNDI Service

>> Interface in your drawings.  I assume it relates to your deployment step
>> 3 "Once the parsing is done the binding in JNDI will occur."  I'm not

>> familiar with JSR 109 so what do you need to bind into JNDI?
>I'm not sure about the JNDI binding either. I am assuming that you 
>intend to look up the (local) home interface in JNDI and invoke using 
>that; however, I do not believe this will work as is as there is a need

>to differentiate between an interface-based invocation and a 
>service-endpoint invocation (see e.g. the operation table on page 100 of
>the EJB2.1 spec).
>It would be possible for the 109 implementation to create the 
>appropriate EJBInvocation directly but that couples the web service 
>proxy to the EJB impl which is probably not a good thing. I think a 
>better alternative would be to have the EJBContainer create a new 
>EJBClientContainer that would handle a web service request from any 109

>impl. Sound feasible?

View raw message