Hi Dims, we agree the changes to axis should be minimal (preferably no changes.)
How we thought about the project is like this .... 1) JSR109 implementation is a tool in axis(like WSDL2Java) which generates a web service that wraps the J2EE components.(a web service that do the lookup and map webservice SEI methods to the EJB ...etc ) It creates a web service that wrap the EJB using the WSDL and the webservice.xml 2)It needs minimal changes to axis (our code is a tool just like WSDL2Java lets say WSDL2J2EE or something). 3) with this tool the axis become JSR109 compliant and the J2EE container is Geronimo. In that case we prefer to stay close with axis. just like a tool (independent piece of code) :) Srianth On Wed, 2003-10-22 at 16:01, Davanum Srinivas wrote: > Srinath, > > The more i think about this, the more i am convinced that most of the work should be > done in > geronimo with minimum changes to axis itself. Since there needs to be tight > integration with > Geronimo and the target is to provide a 109 impl for geronimo. > > Thanks, > dims > > --- Srinath Perera <[EMAIL PROTECTED]> wrote: > > Hi All, > > > > There is a wiki proposal page created for the JSR109 implementation. > > it can be found by url > > > > http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal > > > > Srinath > > > > > ===== > Davanum Srinivas - http://webservices.apache.org/~dims/ >
