As I can see the problem is due to the HTTP binding , some WSDL
validators can not validate HTTP binding. That might be the reason
behind you getting this error. One way to overcome this is to not to
generate the HTTP binding. You can do that by adding the following
parameter.
<parameter name="disableREST">true</parameter >
into your services.xml.
I'm using POJO web service development, and have generated a WSDL using
Java2WSDL, which seems to be invalid. When I import this WSDL into my XML
firewall it says its invalid. I then loaded into XMLSpy to do a validation on
it, and it reports errors:
attribute 'part' in element '<mine: content>' refers to part 'sendFile SWA'
which could not be found in message 'sendFileSWARequest'
So, Here is what I am seeing:
In the message part of the WSDL this is being generated:
<wsdl:message name="sendFileSWARequest">
<wsdl:part name="parameters" element="ns:sendFileSWA"/>
</wsdl:message>
And the operation part of the WSDL, this is being generated:
<wsdl:binding name="SOATestLabServiceHttpBinding"
type="ns:SOATestLabServicePortType">
<http:binding verb="POST"/>
<wsdl:operation name="sendFileSWA">
<http:operation location="SOATestLabService/sendFileSWA"/>
<wsdl:input>
<mime:content type="text/xml" part="sendFileSWA"/>
</wsdl:input>
<wsdl:output>
<mime:content type="text/xml" part="sendFileSWA"/>
</wsdl:output>
</wsdl:operation>
Notice above that the part name is being called 'parameters', and is called that for each and ever message part being generated. However, when the operation section references this message part its being called the name of the method that is invoking this ('sendFileSWA' in this example). It appears that the message parts are not being generated correctly.
For your reference, when I import the WSDL into my Datapower XML Firewall, it
gives me this error:
Fatal Error at line 660: message part sendFileSWA not found.
Attached is my WSDL. How do I get the WSDL to generate properly or is this a bug, or is my firewall being overly strict?
Thanks!
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Thanks,
Deepal
................................................................
http://blogs.deepal.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
