Dims, All. The only one thing I can suggest is that you had mistaken the mailing list address of geronimo-dev.
[EMAIL PROTECTED] ===> [EMAIL PROTECTED] <[EMAIL PROTECTED]> is the right place for you to discuss. Cheers, -- Tetsuya. ([EMAIL PROTECTED]) On Thu, 23 Oct 2003 05:51:29 -0700 (PDT) (Subject: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)) Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Everyone interested....PLEASE join geronimo-dev list. It's time to move the > discussions to just > that mailing list. Please don't CC individuals. Please don't involve axis-user as it > is just a > user group. If and when axis-dev involvement is needed, you can CC that mailing list. > > Thanks, > dims > > --- Guillaume Sauthier <[EMAIL PROTECTED]> wrote: > > Hello > > > > I'm already working on an Axis integration in a J2EE server (JOnAS) for > > a JSR109 implementation. And we found some axis limitations : > > - jaxrpc mapping cannot be completely supported (only package mapping > > and xml type mapping at this time). All stuff concerning class > > generation (class mapping, method mapping) cannot be handled directly > > with WSDL2Java. > > - cannot change endpoint address of a port through the ServiceLocator > > interface. (issu patched recently in CVS) > > > > In short, I'm interrested to contribute for a new Axis tool (like > > WSDL2Java) taking into account the jaxrpc mapping file. After dev, this > > tool should be integrated/used into JOnAS as well as Geronimo... > > > > What do you think ? > > > > Regards > > Guillaume > > > > > > Srinath Perera wrote: > > > > > > 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/ > > > > > > > > > ===== > Davanum Srinivas - http://webservices.apache.org/~dims/ --------------------------------------------------------------------- Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ Apache Software Foundation Committer: http://www.apache.org/~tetsuya/ fingerprint: E420 3713 FAB0 C160 4A1E 6FC5 5846 23D6 80AE BDEA
