So my understanding of this thread is that the proposal now is that these tools tool will form (part of?) a new, separately releasable, module at a peer level to SDO and with a dependency on SDO. I've just proposed a release of SDO and my best guess is that we would be looking at approx 6 weeks time before we are ready to cut a release. What phase in the lifecycle are these tools in; do they have significant pending features to be developed/bugs to fix? I haven't played with them. Can anyone point me to any existing documentation re usage/design/plans?
Kelvin. On 07/02/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote:
Hi, With respect to the Java2WSDL tool I wish to trim quite of bit of it as most of what we need has now been incorporated into the Axis2 tool over which ours has just been a wrapper providing only the missing things. So AFAICT, the only thing that our Java2WSDL wrapper could add over the current version of Axis2 Java2WSDL is the support for SDOs. I hope to get to this as soon as I am done with somethings that I currently tied up with. - Venkat On 2/7/07, Jeremy Boynes <[EMAIL PROTECTED]> wrote: > > Sebastien mentioned stabilizing "tools like WSDL2Java and Java2WSDL > etc." recently and Kelvin and I were previously discussing moving > those tools out of SCA and into SDO on the basis that they actually > don't have any dependency on SCA but do on SDO and EMF. Ant has now > moved them to the axis2 extension, which makes sense given the > dependency on axis2-codegen, but they don't have a dependency on the > other modules in there. > > If there is interest in stabilizing these, then let's move them out > to a separate module and release them when they are done. I assume > that will require a release of SDO first. > > -- > Jeremy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
