You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> on 2003/10/22 11:14:18 UTC
Re: JSR 109 implementation for Apache
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
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi All,
> I would like to see the architecture proposal moved to the wiki (not just
> referenced) so that we can make modifications as our understanding of the
> problem space develops.
> RMH
it is there ..
http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109ProposalArchitecture
and there is a link form the WIKI as well,
regards
Srinath
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Dims,All
I am agreed with dims the jsr109 should be at Geranimo. He is right we
need lot help from Geranimo.
may be if it do not arise any complications the Richard can shepherd us
to Geranimo:) rather than java.net temporary.
Anyway it is nice to have cvs somewhere so we can put our code quickly.
The Ias is working and I have few interfaces to show others as well.
thanks for your time.
regards
Srinath
On Fri, 2003-10-24 at 18:37, Davanum Srinivas wrote:
> Richard,
>
> Yes Please. Shepherd == Coordinate check-ins and review their code/testcases (since they are not
> committers on geronimo)
>
> Thanks,
> dims
>
> --- Richard Monson-Haefel <Ri...@Monson-Haefel.com> wrote:
> > Sorry for the delay. Boy, I take one day off and an entire project gets
> > started while I'm gone. ;-) Looks like its going well, so I'll just jump in.
> >
> > The architecture suggested by Srinath Perera and Ias looks like a good place
> > to start.
> >
> > If no one minds, I'm going to work on item 6 in the proposal. I have
> > requisite understanding of JSR-109 (Just finished a book on the subject) and
> > some ideas of what is needed.
> >
> > I would like to see the architecture proposal moved to the wiki (not just
> > referenced) so that we can make modifications as our understanding of the
> > problem space develops.
> >
> > Anyway, put me down for working on the Wrapper WebService Generator - I'll
> > start by defining what the wrappers should look like and present those ideas
> > to the group when ready.
> >
> > Do you still want me to "Shepherd" Srinath Perera and Ias into the Geronimo
> > project? Not really sure what that means, but I'll be glad to help.
> >
> > RMH
> > --
> > Richard Monson-Haefel
> > Co-Founder\Developer, Apache Geronimo
> > Author of:
> > J2EE Web Services (AW 2003)
> > Enterprise JavaBeans, 4ed (O'Reilly 2004)
> > Java Message Service (O'Reilly 2000)
> > http://www.Monson-Haefel.com
> >
> >
> >
> > On 10/22/03 6:55 AM, in article
> > 20031022115502.30608.qmail@web12808.mail.yahoo.com, "Davanum Srinivas"
> > <di...@apache.org> wrote:
> >
> > > Richard,
> > >
> > > Do you agree with this assessment? We need to bootstrap this pretty quickly
> > > with code from srinath
> > > and Ias. Are you willing to help shepherd them into Geronimo (or) should we do
> > > something in
> > > ws.apache.org? Srinath prefers the latter, but i prefer the former as i see
> > > the need for a tighter
> > > integration and involvement of Geronimo folks.
> > >
> > > Thanks,
> > > dims
> > >>
> >
> >
>
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
Re: JSR 109 implementation for Apache
Posted by Davanum Srinivas <di...@yahoo.com>.
Richard,
Yes Please. Shepherd == Coordinate check-ins and review their code/testcases (since they are not
committers on geronimo)
Thanks,
dims
--- Richard Monson-Haefel <Ri...@Monson-Haefel.com> wrote:
> Sorry for the delay. Boy, I take one day off and an entire project gets
> started while I'm gone. ;-) Looks like its going well, so I'll just jump in.
>
> The architecture suggested by Srinath Perera and Ias looks like a good place
> to start.
>
> If no one minds, I'm going to work on item 6 in the proposal. I have
> requisite understanding of JSR-109 (Just finished a book on the subject) and
> some ideas of what is needed.
>
> I would like to see the architecture proposal moved to the wiki (not just
> referenced) so that we can make modifications as our understanding of the
> problem space develops.
>
> Anyway, put me down for working on the Wrapper WebService Generator - I'll
> start by defining what the wrappers should look like and present those ideas
> to the group when ready.
>
> Do you still want me to "Shepherd" Srinath Perera and Ias into the Geronimo
> project? Not really sure what that means, but I'll be glad to help.
>
> RMH
> --
> Richard Monson-Haefel
> Co-Founder\Developer, Apache Geronimo
> Author of:
> J2EE Web Services (AW 2003)
> Enterprise JavaBeans, 4ed (O'Reilly 2004)
> Java Message Service (O'Reilly 2000)
> http://www.Monson-Haefel.com
>
>
>
> On 10/22/03 6:55 AM, in article
> 20031022115502.30608.qmail@web12808.mail.yahoo.com, "Davanum Srinivas"
> <di...@apache.org> wrote:
>
> > Richard,
> >
> > Do you agree with this assessment? We need to bootstrap this pretty quickly
> > with code from srinath
> > and Ias. Are you willing to help shepherd them into Geronimo (or) should we do
> > something in
> > ws.apache.org? Srinath prefers the latter, but i prefer the former as i see
> > the need for a tighter
> > integration and involvement of Geronimo folks.
> >
> > Thanks,
> > dims
> >>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Sorry for the delay. Boy, I take one day off and an entire project gets
started while I'm gone. ;-) Looks like its going well, so I'll just jump in.
The architecture suggested by Srinath Perera and Ias looks like a good place
to start.
If no one minds, I'm going to work on item 6 in the proposal. I have
requisite understanding of JSR-109 (Just finished a book on the subject) and
some ideas of what is needed.
I would like to see the architecture proposal moved to the wiki (not just
referenced) so that we can make modifications as our understanding of the
problem space develops.
Anyway, put me down for working on the Wrapper WebService Generator - I'll
start by defining what the wrappers should look like and present those ideas
to the group when ready.
Do you still want me to "Shepherd" Srinath Perera and Ias into the Geronimo
project? Not really sure what that means, but I'll be glad to help.
RMH
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com
On 10/22/03 6:55 AM, in article
20031022115502.30608.qmail@web12808.mail.yahoo.com, "Davanum Srinivas"
<di...@apache.org> wrote:
> Richard,
>
> Do you agree with this assessment? We need to bootstrap this pretty quickly
> with code from srinath
> and Ias. Are you willing to help shepherd them into Geronimo (or) should we do
> something in
> ws.apache.org? Srinath prefers the latter, but i prefer the former as i see
> the need for a tighter
> integration and involvement of Geronimo folks.
>
> Thanks,
> dims
>>
Re: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@yahoo.com>.
Yes, my mistake. thanks for the catch.
-- dims
--- Tetsuya Kitahata <te...@apache.org> wrote:
>
> Dims, All.
>
> The only one thing I can suggest is that you had mistaken the mailing
> list address of geronimo-dev.
>
> geronimo-dev@ws.apache.org
> ===>
> geronimo-dev@incubator.apache.org
>
> <ge...@incubator.apache.org> is the right place
> for you to discuss.
>
> Cheers,
>
> -- Tetsuya. (tetsuya@apache.org)
>
> On Thu, 23 Oct 2003 05:51:29 -0700 (PDT)
> (Subject: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache))
> Davanum Srinivas <di...@apache.org> 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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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: tetsuya@apache.org 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
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@yahoo.com>.
Yes, my mistake. thanks for the catch.
-- dims
--- Tetsuya Kitahata <te...@apache.org> wrote:
>
> Dims, All.
>
> The only one thing I can suggest is that you had mistaken the mailing
> list address of geronimo-dev.
>
> geronimo-dev@ws.apache.org
> ===>
> geronimo-dev@incubator.apache.org
>
> <ge...@incubator.apache.org> is the right place
> for you to discuss.
>
> Cheers,
>
> -- Tetsuya. (tetsuya@apache.org)
>
> On Thu, 23 Oct 2003 05:51:29 -0700 (PDT)
> (Subject: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache))
> Davanum Srinivas <di...@apache.org> 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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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: tetsuya@apache.org 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
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Tetsuya Kitahata <te...@apache.org>.
Dims, All.
The only one thing I can suggest is that you had mistaken the mailing
list address of geronimo-dev.
geronimo-dev@ws.apache.org
===>
geronimo-dev@incubator.apache.org
<ge...@incubator.apache.org> is the right place
for you to discuss.
Cheers,
-- Tetsuya. (tetsuya@apache.org)
On Thu, 23 Oct 2003 05:51:29 -0700 (PDT)
(Subject: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache))
Davanum Srinivas <di...@apache.org> 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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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: tetsuya@apache.org 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
Re: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Tetsuya Kitahata <te...@apache.org>.
Dims, All.
The only one thing I can suggest is that you had mistaken the mailing
list address of geronimo-dev.
geronimo-dev@ws.apache.org
===>
geronimo-dev@incubator.apache.org
<ge...@incubator.apache.org> is the right place
for you to discuss.
Cheers,
-- Tetsuya. (tetsuya@apache.org)
On Thu, 23 Oct 2003 05:51:29 -0700 (PDT)
(Subject: Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache))
Davanum Srinivas <di...@apache.org> 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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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: tetsuya@apache.org 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
RE: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Luis
On Fri, 2003-10-24 at 00:15, knight@adsl.tie.cl wrote:
>We need the same kind of hook in JSR-109 impl that exist in Axis for the
> deployment.
please let us know what is the best place to find the DD
architecture info. and from following what does Geronimo support right now.
1)WSDL (??)
2)jaxrpcmapping(no?)
3)ejb xml file (yes?)
4)web service.xml (no?)
We will write code to support what Geronimo not support now. Are we add
that code to Geronimo DD parsing module
> Our proposal consist , basically, in make a JMX layer that allow any JSR-109
> compliant ws-engine to be integrated with geronimo.
and to commnet about this I think it is better to take axis-dev in I cc
to axis dev.
Srinath
>
> We think that we'll soon be able to do an arquitectural proposal.
>
> We agree with you, and it has alway been our idea since the begining: we
> need a clear interface, this manner, Axis must be considered as a service
> like the others.
>
> Our job proposal consist in two steps:
>
> As a first step, we are going to integrate Axis as it is. Then
> we'll work closely with the team in charge of the JSR-109 implementation
> to globally integrate JSR-109 to geronimo.
>
> Jeremy Lemaire sent a prior message with the same concepts, but i prefered
> to explain they again.
>
> Luis Avila
>
> >-- Original Message --
> >Reply-To: geronimo-dev@incubator.apache.org
> >From: "Jeremy Boynes" <je...@coredevelopers.net>
> >To: <ge...@incubator.apache.org>
> >Cc: <he...@vijayaba.cse.mrt.ac.lk>
> >Subject: RE: JSR 109 implementation for Apache
> >Date: Thu, 23 Oct 2003 06:33:07 -0700
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Srinath Perera [mailto:hemapani@vijayaba.cse.mrt.ac.lk]
> >> Sent: Thursday, October 23, 2003 2:01 AM
> >>
> >> > After dev, this
> >> > tool should be integrated/used into JOnAS as well as Geronimo...
> >> >
> >> > What do you think ?
> >>
> >
> >Definitely a good goal.
> >
> >> sure :) we are more than happy to have your help ..
> >> I remember you mention there are some part of code you have which
> >> might be reused in a JSR109 impl as well.
> >>
> >> here is architecture propsal (you might have seen)
> >>
> >> http://www.cse.mrt.ac.lk/~hemapani/JSR109/architecture.html
> >>
> >> yap and if my understanding is correct this can be used in
> >> the JOnAs as well
> >> as geranimo. (actually in that way it depends on the J2EE
> >> spec not the container. My only concern is will it be a big
> >> performence penalty as we do first an
> >> HTTP/SOAP access(web service layer) then RMI accsess.(axis to
> >> container)
> >> / if this is a problem we can use Local inteface instead of Remote
> >> interface(just a idea))
> >>
> >
> >I can't think of any reason why that should not be possible. You
> >probably want to support both though to allow for configurations where
> >the web-services gateway is running on a dedicated machine.
> >
> >A couple of comments on the architecture page:
> >
> >I don't see any mention of client side support (e.g. using a web service
> >from an EJB) - is this something you are planning to address?
> >
> >You should hook the XML parsing stuff into Geronimo's deployment
> >mechanism - I believe Aaron Mulder was already asking what, if any,
> >additional elements were needed in the vendor DDs. We want to avoid the
> >case where the same XML gets parsed many times by many services. This
> >should also be integrated with Geronimo's MBean model so that the web
> >services specific components are manageable.
> >
> >Can you define the hooks into the security services e.g. how you would
> >support future message level authentication (I would like to know we had
> >at least considered some of the security issues).
> >
> >--
> >Jeremy
> >
>
RE: JSR 109 implementation for Apache
Posted by kn...@adsl.tie.cl.
We need the same kind of hook in JSR-109 impl that exist in Axis for the
deployment.
Our proposal consist , basically, in make a JMX layer that allow any JSR-109
compliant ws-engine to be integrated with geronimo.
We think that we'll soon be able to do an arquitectural proposal.
We agree with you, and it has alway been our idea since the begining: we
need a clear interface, this manner, Axis must be considered as a service
like the others.
Our job proposal consist in two steps:
As a first step, we are going to integrate Axis as it is. Then
we'll work closely with the team in charge of the JSR-109 implementation
to globally integrate JSR-109 to geronimo.
Jeremy Lemaire sent a prior message with the same concepts, but i prefered
to explain they again.
Luis Avila
>-- Original Message --
>Reply-To: geronimo-dev@incubator.apache.org
>From: "Jeremy Boynes" <je...@coredevelopers.net>
>To: <ge...@incubator.apache.org>
>Cc: <he...@vijayaba.cse.mrt.ac.lk>
>Subject: RE: JSR 109 implementation for Apache
>Date: Thu, 23 Oct 2003 06:33:07 -0700
>
>
>
>
>> -----Original Message-----
>> From: Srinath Perera [mailto:hemapani@vijayaba.cse.mrt.ac.lk]
>> Sent: Thursday, October 23, 2003 2:01 AM
>>
>> > After dev, this
>> > tool should be integrated/used into JOnAS as well as Geronimo...
>> >
>> > What do you think ?
>>
>
>Definitely a good goal.
>
>> sure :) we are more than happy to have your help ..
>> I remember you mention there are some part of code you have which
>> might be reused in a JSR109 impl as well.
>>
>> here is architecture propsal (you might have seen)
>>
>> http://www.cse.mrt.ac.lk/~hemapani/JSR109/architecture.html
>>
>> yap and if my understanding is correct this can be used in
>> the JOnAs as well
>> as geranimo. (actually in that way it depends on the J2EE
>> spec not the container. My only concern is will it be a big
>> performence penalty as we do first an
>> HTTP/SOAP access(web service layer) then RMI accsess.(axis to
>> container)
>> / if this is a problem we can use Local inteface instead of Remote
>> interface(just a idea))
>>
>
>I can't think of any reason why that should not be possible. You
>probably want to support both though to allow for configurations where
>the web-services gateway is running on a dedicated machine.
>
>A couple of comments on the architecture page:
>
>I don't see any mention of client side support (e.g. using a web service
>from an EJB) - is this something you are planning to address?
>
>You should hook the XML parsing stuff into Geronimo's deployment
>mechanism - I believe Aaron Mulder was already asking what, if any,
>additional elements were needed in the vendor DDs. We want to avoid the
>case where the same XML gets parsed many times by many services. This
>should also be integrated with Geronimo's MBean model so that the web
>services specific components are manageable.
>
>Can you define the hooks into the security services e.g. how you would
>support future message level authentication (I would like to know we had
>at least considered some of the security issues).
>
>--
>Jeremy
>
RE: JSR 109 implementation for Apache
Posted by Jeremy Boynes <je...@coredevelopers.net>.
> -----Original Message-----
> From: Srinath Perera [mailto:hemapani@vijayaba.cse.mrt.ac.lk]
> Sent: Thursday, October 23, 2003 2:01 AM
>
> > After dev, this
> > tool should be integrated/used into JOnAS as well as Geronimo...
> >
> > What do you think ?
>
Definitely a good goal.
> sure :) we are more than happy to have your help ..
> I remember you mention there are some part of code you have which
> might be reused in a JSR109 impl as well.
>
> here is architecture propsal (you might have seen)
>
> http://www.cse.mrt.ac.lk/~hemapani/JSR109/architecture.html
>
> yap and if my understanding is correct this can be used in
> the JOnAs as well
> as geranimo. (actually in that way it depends on the J2EE
> spec not the container. My only concern is will it be a big
> performence penalty as we do first an
> HTTP/SOAP access(web service layer) then RMI accsess.(axis to
> container)
> / if this is a problem we can use Local inteface instead of Remote
> interface(just a idea))
>
I can't think of any reason why that should not be possible. You
probably want to support both though to allow for configurations where
the web-services gateway is running on a dedicated machine.
A couple of comments on the architecture page:
I don't see any mention of client side support (e.g. using a web service
from an EJB) - is this something you are planning to address?
You should hook the XML parsing stuff into Geronimo's deployment
mechanism - I believe Aaron Mulder was already asking what, if any,
additional elements were needed in the vendor DDs. We want to avoid the
case where the same XML gets parsed many times by many services. This
should also be integrated with Geronimo's MBean model so that the web
services specific components are manageable.
Can you define the hooks into the security services e.g. how you would
support future message level authentication (I would like to know we had
at least considered some of the security issues).
--
Jeremy
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Guillaume,
In short, I'm interrested to contribute for a new Axis tool (like
> WSDL2Java) taking into account the jaxrpc mapping file.
JAX-RPC mapping file is a requirement for JSR109 spec we have to support
it anyway I think.
> After dev, this
> tool should be integrated/used into JOnAS as well as Geronimo...
>
> What do you think ?
sure :) we are more than happy to have your help ..
I remember you mention there are some part of code you have which
might be reused in a JSR109 impl as well.
here is architecture propsal (you might have seen)
http://www.cse.mrt.ac.lk/~hemapani/JSR109/architecture.html
yap and if my understanding is correct this can be used in the JOnAs as well
as geranimo. (actually in that way it depends on the J2EE spec not the container.
My only concern is will it be a big performence penalty as we do first an
HTTP/SOAP access(web service layer) then RMI accsess.(axis to container)
/ if this is a problem we can use Local inteface instead of Remote
interface(just a idea))
that is something I really need to discuss.
Srinath
On Thu, 2003-10-23 at 14:11, Guillaume Sauthier 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> > >
>
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
Hi Guillaume,
In short, I'm interrested to contribute for a new Axis tool (like
> WSDL2Java) taking into account the jaxrpc mapping file.
JAX-RPC mapping file is a requirement for JSR109 spec we have to support
it anyway I think.
> After dev, this
> tool should be integrated/used into JOnAS as well as Geronimo...
>
> What do you think ?
sure :) we are more than happy to have your help ..
I remember you mention there are some part of code you have which
might be reused in a JSR109 impl as well.
here is architecture propsal (you might have seen)
http://www.cse.mrt.ac.lk/~hemapani/JSR109/architecture.html
yap and if my understanding is correct this can be used in the JOnAs as well
as geranimo. (actually in that way it depends on the J2EE spec not the container.
My only concern is will it be a big performence penalty as we do first an
HTTP/SOAP access(web service layer) then RMI accsess.(axis to container)
/ if this is a problem we can use Local inteface instead of Remote
interface(just a idea))
that is something I really need to discuss.
Srinath
On Thu, 2003-10-23 at 14:11, Guillaume Sauthier 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> > >
>
Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@apache.org>.
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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
Ias wrote:
>
> > 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)
> >
> Those were exactly what I had to figure out. Now my prototype,
> org.apache.ws4j2ee.jaxrpcmapping delivers Wsdl2J2ee, J2eeEmitter, and
> J2eeXxxWriters different from those of org.apache.axis.wsdl.toJava. On the
> other hand, the new WSDL processor is based on Axis' WSDL2 framework, so you
> can consider this JAX-RPC mapping file parser as an customized extension of
> the framework.
That's how I figure the thing...
At this time, I use only the WSDL2Java tool to generate client sides
classes.
In addition to this, I generate server-config.wsdd files defining a list
of service, with jaxrpc handler from webservices.xml, ejb-jar.xml /
web.xml and mapping file (use package mapping and xml type mapping).
And same thing for the client-config.wsdd from web.xml/ejb-jar.xml
(service-ref) for the jaxrpc handler specified in service-ref.
I had to write my own EngineConfigurationFactory to load specified wsdd,
not default ones.
>
> > 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...
> >
>
> Please see JSR109Proposal at
> http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal also including
> JAX-RPC mapping file parser proposal. I'm quite convinced that JOnAs also
> can make the full use of the parser.
I've seen this. Looks Greats. It's a big work !
Sure JOnAS can use this as replacement for WSDL2Java ...
>
> Thanks for your interest,
>
> Ias
RE: JSR 109 implementation for Apache
Posted by Ias <ia...@tmax.co.kr>.
> 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)
>
Those were exactly what I had to figure out. Now my prototype,
org.apache.ws4j2ee.jaxrpcmapping delivers Wsdl2J2ee, J2eeEmitter, and
J2eeXxxWriters different from those of org.apache.axis.wsdl.toJava. On the
other hand, the new WSDL processor is based on Axis' WSDL2 framework, so you
can consider this JAX-RPC mapping file parser as an customized extension of
the framework.
> 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...
>
Please see JSR109Proposal at
http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal also including
JAX-RPC mapping file parser proposal. I'm quite convinced that JOnAs also
can make the full use of the parser.
Thanks for your interest,
Ias
Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@apache.org>.
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 <Gu...@Objectweb.org> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> >
Re: JSR 109 implementation for Apache
Posted by Guillaume Sauthier <Gu...@Objectweb.org>.
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> >
Re: JSR 109 implementation for Apache
Posted by Davanum Srinivas <di...@apache.org>.
Richard,
Do you agree with this assessment? We need to bootstrap this pretty quickly with code from srinath
and Ias. Are you willing to help shepherd them into Geronimo (or) should we do something in
ws.apache.org? Srinath prefers the latter, but i prefer the former as i see the need for a tighter
integration and involvement of Geronimo folks.
Thanks,
dims
--- Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@apache.org>.
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
--- Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> wrote:
> sorry if I give a false hope ...it was archtecture I was explainig. Code
> is not written yet be have fairly good idea what to done and the
> architecture.(I belive) We will start writing it once the discussion
> done.
>
> Srinath
>
> On Thu, 2003-10-23 at 09:29, Richard Monson-Haefel wrote:
> > Sounds interesting. Is the code available somewhere for us to look at?
> >
> > On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
> > 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Move discussions to geronimo-dev@ (Re: JSR 109 implementation for Apache)
Posted by Davanum Srinivas <di...@apache.org>.
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
--- Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> wrote:
> sorry if I give a false hope ...it was archtecture I was explainig. Code
> is not written yet be have fairly good idea what to done and the
> architecture.(I belive) We will start writing it once the discussion
> done.
>
> Srinath
>
> On Thu, 2003-10-23 at 09:29, Richard Monson-Haefel wrote:
> > Sounds interesting. Is the code available somewhere for us to look at?
> >
> > On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
> > 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
sorry if I give a false hope ...it was archtecture I was explainig. Code
is not written yet be have fairly good idea what to done and the
architecture.(I belive) We will start writing it once the discussion
done.
Srinath
On Thu, 2003-10-23 at 09:29, Richard Monson-Haefel wrote:
> Sounds interesting. Is the code available somewhere for us to look at?
>
> On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> >>
> >
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
sorry if I give a false hope ...it was archtecture I was explainig. Code
is not written yet be have fairly good idea what to done and the
architecture.(I belive) We will start writing it once the discussion
done.
Srinath
On Thu, 2003-10-23 at 09:29, Richard Monson-Haefel wrote:
> Sounds interesting. Is the code available somewhere for us to look at?
>
> On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
> >>
> >
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Sounds interesting. Is the code available somewhere for us to look at?
On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
>>
>
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Sounds interesting. Is the code available somewhere for us to look at?
On 10/22/03 5:41 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
>>
>
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com
Re: JSR 109 implementation for Apache
Posted by Davanum Srinivas <di...@apache.org>.
Richard,
Do you agree with this assessment? We need to bootstrap this pretty quickly with code from srinath
and Ias. Are you willing to help shepherd them into Geronimo (or) should we do something in
ws.apache.org? Srinath prefers the latter, but i prefer the former as i see the need for a tighter
integration and involvement of Geronimo folks.
Thanks,
dims
--- Srinath Perera <he...@vijayaba.cse.mrt.ac.lk> 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
>
Re: JSR 109 implementation for Apache
Posted by Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>.
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 <he...@vijayaba.cse.mrt.ac.lk> 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/
>
Re: JSR 109 implementation for Apache
Posted by Davanum Srinivas <di...@apache.org>.
Srinath,
The more i think about this, the more i am convinced that most of the work should be done in
geronimo with minumum 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Looks good. I'm out today but will be back on this tomorrow.
On 10/22/03 4:14 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
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
>
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Thanks, I'm working on some other things today and will join the discussion
tomorrow night.
On 10/22/03 4:14 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
wrote:
> http://nagoya.apache.org/wiki/apachewiki.cgi?JSR109Proposal
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com
Re: JSR 109 implementation for Apache
Posted by Davanum Srinivas <di...@apache.org>.
Srinath,
The more i think about this, the more i am convinced that most of the work should be done in
geronimo with minumum 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 <he...@vijayaba.cse.mrt.ac.lk> 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/
Re: JSR 109 implementation for Apache
Posted by Richard Monson-Haefel <Ri...@Monson-Haefel.com>.
Looks good. I'm out today but will be back on this tomorrow.
On 10/22/03 4:14 AM, "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk>
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
>
--
Richard Monson-Haefel
Co-Founder\Developer, Apache Geronimo
Author of:
J2EE Web Services (AW 2003)
Enterprise JavaBeans, 4ed (O'Reilly 2004)
Java Message Service (O'Reilly 2000)
http://www.Monson-Haefel.com