There's no detailed information in the JIRA about the problems with the WSDL that's generated currently. Would they affect interoperability, or are they just cosmetic? If they are just cosmetic, then deferring this fix to post-1.0 should not be a problem. If they could affect interoperability when we make the WSDL conform to the spec, then I'd be more concerned about deferring it.
Simon Jean-Sebastien Delfino (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TUSCANY-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Sebastien Delfino updated TUSCANY-1648: -------------------------------------------- Fix Version/s: (was: Java-SCA-1.0) Java-SCA-Next Moving to SCA-Next as these JIRAs are not likely to be fixed by 1.0.WS Binding WSDL generation should follow the rules in section 2.3.5 of the WS binding spec ------------------------------------------------------------------------------------------ Key: TUSCANY-1648 URL: https://issues.apache.org/jira/browse/TUSCANY-1648 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-0.99 Reporter: Jean-Sebastien Delfino Fix For: Java-SCA-Next The WSDL automatically generated by the Web Service binding should be generated as described in section 2.3.5 of the WS binding specification.Our current WSDL generation algorithm generates valid WSDL, but different from what's described in the SCA spec.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
