On 6/13/07, Ron Gavlin <[EMAIL PROTECTED]> wrote:
One way to expand the visibility and adoption of SDO within the broader community is to improve its integration story with external projects. A few projects in particular seem obvious, namely the Spring Framework, Apache CXF, and Apache Axis2. Some of this work might simply be documentation. In other cases, integration/glue code might be needed. Is this type of work outside the scope of Tuscany SDO? If not, would Tuscany SDO consider hosting this type of integration code until such a time as the external projects decided to host it themselves? Any thoughts? - Ron
Yes! +1, would be a really really good thing to do. In fact, I think we really *must* to do this for Axis2 to sort out our SCA Java2WSDL/WSDL2Java tooling story properly as right now its a bit of a mess. The Axis2 databinding framework is designed to be completely plugable but instead of using that the Tuscany Java2WSDL and WSDL2Java tools copied and changed various Axis2 classes to add in SDO support. That doesn't work that well and always causes problems every time we update the Axis2 release we use. Making SDO a first class Axis2 databinding would fix those problems, it would also enable the Tuscany Java2WSDL/WSDL2Java tools to work with the other Axis2 supported databindings like JAXB, and it would "expand the visibility and adoption of SDO within the broader community". Would you like to help get it done? I'd been planning on focusing on WS in the release after the upcoming SCA 0.91 release so the timing for this is good. It needs a bit of new integration code but its not a huge amount. We could host it in Tuscany to start with but probably eventually donate it to be included within Axis2 itself. We've even an old JIRA where this almost got started on and that points to some emails with more detail: https://issues.apache.org/jira/browse/TUSCANY-1038 ...ant
