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 - [EMAIL PROTECTED] -----Original Message----- From: ant elder [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
