Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 184937

Summary: Axis2: WSDL file generated by Axis2 contains validation error
Product: [WebTools] WTP Webservices Reporter: Kathy Chan <kathy>
Component: jst.wsAssignee: 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 Flags
Echo.wsdl generated by Axis2 none

Description Kathy Chan CLA 2007-05-01 13:52:57 EDT
The WSDL file generated by the Axis2 runtime contains:

<wsdl:binding name="EchoHttpBinding" type="axis2:EchoPortType">
		<http:binding verb="POST" />
		<wsdl:operation name="hello">
			<http:operation location="hello" />
			<wsdl:input>
				<mime:content type="text/xml" />
			</wsdl:input>
			<wsdl:output>
				<mime:content type="text/xml" />
			</wsdl:output>
		</wsdl:operation>
	</wsdl:binding>

which caused a validation error:

Severity and Description	Path	Resource	Location	Creation Time	Id
cvc-complex-type.4: Attribute 'part' must appear on element 'mime:content'.	c3AllTypes/WebContent	Echo.wsdl	line 16	1178036376861	1350

This section from the Attachment profile 1.0 mandates the part:

4.9 WSDL Parts
R2910 A mime:content in a DESCRIPTION MUST reference a wsdl:part that is defined using either the type attribute or the element attribute

The MIME schema at:

http://ws-i.org/profiles/basic/1.1/wsdlmime-2004-08-24.xsd

specifies that the part attribute is required.

We are still trying to clarify on this issue.  If the part attribute is really required, then we should open an Axis JIRA to ask for the generated WSDL file to be changed to not cause the validation message.  Otherwise, the WSDL/schema validator should be loosen to not flag that as an error.
Comment 1 Kathy Chan CLA 2007-05-01 13:56:17 EDT
Created attachment 65500 [details]
Echo.wsdl generated by Axis2
Comment 2 Kathy Chan CLA 2007-05-02 10:24:18 EDT
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.
Comment 3 Lahiru Sandakith CLA 2007-05-02 12:30:24 EDT
JIRA created on Axis2 for the wsdl validation error

https://issues.apache.org/jira/browse/AXIS2-2630

will follow up this 

Thanks 

Lahiru
Comment 4 Lahiru Sandakith CLA 2007-05-02 12:33:30 EDT
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

Comment 5 Lahiru Sandakith CLA 2007-05-30 09:49:23 EDT
(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
Comment 6 Lahiru Sandakith CLA 2007-06-13 02:09:12 EDT
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. 
Comment 7 Kathy Chan CLA 2007-06-13 09:18:25 EDT
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.
Comment 8 Lahiru Sandakith CLA 2007-06-14 07:26:35 EDT
Axis2 nightly builds are available here
http://people.apache.org/dist/axis2/nightly/

Lahiru
Comment 9 Lahiru Sandakith CLA 2007-08-26 23:07:38 EDT
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 
Comment 10 David Holscher CLA 2008-03-17 12:35:45 EDT
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.
Comment 11 Kathy Chan CLA 2008-07-16 18:40:29 EDT
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.
Comment 12 Kathy Chan CLA 2008-07-16 20:04:40 EDT
Closing.