You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2007/08/08 20:47:23 UTC
Java2WSDL/WSDL2Java tools
Our Java2WSDL and WSDL2Java tools have been a bit neglected and thats
starting to get a few comments, so what should we do with these? Is the
intention that these are specifically for SDO or should they be more general
tools with options to be compatible with all the data binding's that Tuscany
SCA supports? The ws binding generating wsdl on the fly seems related to
Java2WSDL, do we expect the wsdl be identical whether generated on the fly
or from java2wsdl? Should the on the fly generation and java2wsdl tool share
any common code? There's also the java/xsd tools on the SDO project, should
any of that code get used by the SCA tools when using SDOs?
...ant
Re: Java2WSDL/WSDL2Java tools
Posted by kelvin goodson <ke...@gmail.com>.
sounds sensible to me, +1 to handling this within Axis2.
Kelvin.
On 09/08/07, ant elder <an...@gmail.com> wrote:
> Thats right, these are the Axis2 tools just with some patches on top to add
> support for SDOs and to fix bugs we've come across before we got the bugs
> fixed in the Axis2 code. The problem with doing it like this has been we
> fall be hind Axis2 and loose track of what we changed and its a headache to
> merge things each time there's a new Axis2 release, which is why our
> versions have slipped behind like this. I agree we should do just as you say
> and work more closely with Axis2, ideally make SDO a first class Axis2
> databinding so we don't even need to modify the Axis2 code. Thats kind of
> why I started this thread - to prompt some discussion on what we want this
> tooling to be doing.
>
> ...ant
>
> On 8/8/07, Brady Johnson <bj...@roguewave.com> wrote:
> >
> >
> > I thought I saw a post recently where someone mentioned that these tools
> > were "taken from" axis. If so, are we going to maintain a parallel
> > implementation? It might be useful to talk with the axis folks to see if
> > these tools can be refactored in such a way as to easily allow the types
> > of extensions/additions that Tuscany will be doing, thus avoiding
> > duplicate code.
> >
> > On another note:
> > Has anyone ever seen the same tools for C++? If not, maybe we could open
> > another thread to discuss implementing them for TuscanySCA Native.
> >
> >
> > --------------------
> > Brady Johnson
> > Lead Software Developer - HydraSCA
> > Rogue Wave Software - brady.johnson@roguewave.com
> >
> >
> > -----Original Message-----
> > From: ant elder [mailto:ant.elder@gmail.com]
> > Sent: Wednesday, August 08, 2007 12:47 PM
> > To: tuscany-dev
> > Subject: Java2WSDL/WSDL2Java tools
> >
> > Our Java2WSDL and WSDL2Java tools have been a bit neglected and thats
> > starting to get a few comments, so what should we do with these? Is the
> > intention that these are specifically for SDO or should they be more
> > general tools with options to be compatible with all the data binding's
> > that Tuscany SCA supports? The ws binding generating wsdl on the fly
> > seems related to Java2WSDL, do we expect the wsdl be identical whether
> > generated on the fly or from java2wsdl? Should the on the fly generation
> > and java2wsdl tool share any common code? There's also the java/xsd
> > tools on the SDO project, should any of that code get used by the SCA
> > tools when using SDOs?
> >
> > ...ant
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Java2WSDL/WSDL2Java tools
Posted by ant elder <an...@gmail.com>.
Thats right, these are the Axis2 tools just with some patches on top to add
support for SDOs and to fix bugs we've come across before we got the bugs
fixed in the Axis2 code. The problem with doing it like this has been we
fall be hind Axis2 and loose track of what we changed and its a headache to
merge things each time there's a new Axis2 release, which is why our
versions have slipped behind like this. I agree we should do just as you say
and work more closely with Axis2, ideally make SDO a first class Axis2
databinding so we don't even need to modify the Axis2 code. Thats kind of
why I started this thread - to prompt some discussion on what we want this
tooling to be doing.
...ant
On 8/8/07, Brady Johnson <bj...@roguewave.com> wrote:
>
>
> I thought I saw a post recently where someone mentioned that these tools
> were "taken from" axis. If so, are we going to maintain a parallel
> implementation? It might be useful to talk with the axis folks to see if
> these tools can be refactored in such a way as to easily allow the types
> of extensions/additions that Tuscany will be doing, thus avoiding
> duplicate code.
>
> On another note:
> Has anyone ever seen the same tools for C++? If not, maybe we could open
> another thread to discuss implementing them for TuscanySCA Native.
>
>
> --------------------
> Brady Johnson
> Lead Software Developer - HydraSCA
> Rogue Wave Software - brady.johnson@roguewave.com
>
>
> -----Original Message-----
> From: ant elder [mailto:ant.elder@gmail.com]
> Sent: Wednesday, August 08, 2007 12:47 PM
> To: tuscany-dev
> Subject: Java2WSDL/WSDL2Java tools
>
> Our Java2WSDL and WSDL2Java tools have been a bit neglected and thats
> starting to get a few comments, so what should we do with these? Is the
> intention that these are specifically for SDO or should they be more
> general tools with options to be compatible with all the data binding's
> that Tuscany SCA supports? The ws binding generating wsdl on the fly
> seems related to Java2WSDL, do we expect the wsdl be identical whether
> generated on the fly or from java2wsdl? Should the on the fly generation
> and java2wsdl tool share any common code? There's also the java/xsd
> tools on the SDO project, should any of that code get used by the SCA
> tools when using SDOs?
>
> ...ant
>
RE: Java2WSDL/WSDL2Java tools
Posted by Brady Johnson <bj...@roguewave.com>.
I thought I saw a post recently where someone mentioned that these tools
were "taken from" axis. If so, are we going to maintain a parallel
implementation? It might be useful to talk with the axis folks to see if
these tools can be refactored in such a way as to easily allow the types
of extensions/additions that Tuscany will be doing, thus avoiding
duplicate code.
On another note:
Has anyone ever seen the same tools for C++? If not, maybe we could open
another thread to discuss implementing them for TuscanySCA Native.
--------------------
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - brady.johnson@roguewave.com
-----Original Message-----
From: ant elder [mailto:ant.elder@gmail.com]
Sent: Wednesday, August 08, 2007 12:47 PM
To: tuscany-dev
Subject: Java2WSDL/WSDL2Java tools
Our Java2WSDL and WSDL2Java tools have been a bit neglected and thats
starting to get a few comments, so what should we do with these? Is the
intention that these are specifically for SDO or should they be more
general tools with options to be compatible with all the data binding's
that Tuscany SCA supports? The ws binding generating wsdl on the fly
seems related to Java2WSDL, do we expect the wsdl be identical whether
generated on the fly or from java2wsdl? Should the on the fly generation
and java2wsdl tool share any common code? There's also the java/xsd
tools on the SDO project, should any of that code get used by the SCA
tools when using SDOs?
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org