| Summary: | Axis2: WSDL file generated by Axis2 contains validation error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Kathy Chan <kathy> | ||||
| Component: | jst.ws | Assignee: | Lahiru Sandakith <sandakith> | ||||
| Status: | CLOSED FIXED | QA Contact: | Chris Brealey <cbrealey> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | David.Holscher, project-eclipse, valentinbaciu | ||||
| Version: | 2.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Kathy Chan
Created attachment 65500 [details]
Echo.wsdl generated by Axis2
Note from Christopher Ferris confirmed that: Basically, this is considered a correction over the original schema. It made no sense to omit the part attribute under any circumstance. Thus, we changed the schema accordingly. True, there can be non-cnformant WSDLs, but in this case, they would make no sense. So, please open a JIRA on Axis2 to have it generate WSDL that does not contain this error. JIRA created on Axis2 for the wsdl validation error https://issues.apache.org/jira/browse/AXIS2-2630 will follow up this Thanks Lahiru adding cc to project-eclipse@lists.wso2.com JIRA created on Axis2 for the wsdl validation error https://issues.apache.org/jira/browse/AXIS2-2630 (In reply to comment #4) > adding cc to project-eclipse@lists.wso2.com > > JIRA created on Axis2 for the wsdl validation error > > https://issues.apache.org/jira/browse/AXIS2-2630 > The Issue is fixed in the current Axis2 SVN trunk. Thank s Lahiru https://issues.apache.org/jira/browse/AXIS2-2630 This issue was resolved in the Axis2 head, Testing with the axis2 nightly build resulted no errors in the wsdl validation. Resolving the issue. Reopening defect as this Axis2 nightly build is not available for public consumption yet. Please resolve this bug when this fix makes it in an Axis2 release. When it does, please specify the release name containing this fix. For the time being, you could also specify where to get the Axis2 nightly build that contain this fix. Axis2 nightly builds are available here http://people.apache.org/dist/axis2/nightly/ Lahiru Hi The issue has been fixed on Axis2 - https://issues.apache.org/jira/browse/AXIS2-2630 its on Axis-1.3 to varify and also nightly builds are available on http://people.apache.org/dist/axis2/nightly/ Please verify and close the issue. Thanks Lahiru I do not believe the WSDL as originally generated should result in a validation error. The binding here is an HTTP POST which should not be validated for WS-I compliance as HTTP POST is not part of BP or SSBP but it is allowed to appear: In SSBP 4.1: "Note that this places a requirement on the construction of conformant wsdl:binding elements. It does not place a requirement on descriptions as a whole; in particular, it does not preclude WSDL documents from containing non-conformant wsdl:binding elements." The annoying bit is that the .NET platform likes to create HTTP POST and GET bindings along with the SOAP binding for every service. If you keep this validation error then every .NET service someone imports the WSDL for will get this validation error. I tried with Axis2 v1.4 and the WDSL file generated does not have this error anymore. David, please open a defect on the wst.wsi component for comment #10 and we can carry on the discussion of whether the validation should be there or not for HTTP Post. Closing. |