Return Element Wsdl Problem
See original GitHub issueIn version 1.0.0, return type not contains xs:complexType and xs:sequence. And wsdl format not validated in Oxygen XML Editor.
In version 0.9.9.6 Wsdl Output:
<xs:element name="sampleMethodResponse">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="sampleMethodResult" type="tns:sampleMethodC"/>
</xs:sequence>
</xs:complexType>
</xs:element>
But in version 1.0.0 Wsdl Output:
<xs:element name="sampleMethodResponse">
<xs:element minOccurs="0" maxOccurs="1" name="sampleMethodResult" type="tns:sampleMethodC"/>
</xs:element>
How can I get xs:complexType and xs:sequence?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Cannot find the declaration of element 'wsdl:definitions'
I have tried to search a solution to my problem and didn't succeed. When I am trying to validate my XML file with...
Read more >How to parse WSDL (Error: Failed to parse wsdl: Unknown ...
I've been working on a tool that extends the Apex support for WSDLs without the need to manually manipulate the WSDL before hand....
Read more >Error: Failed to parse WSDL: Unable to find complexType ...
I'm one of the current maintainers of SFDC Explorer. The reason the generated Apex classes do not validate is that your string types...
Read more >WSDL contains element with name: Return
Hi, I have a big problem with the automatic code generation for a web service. ... The WSDL contains an element that is...
Read more >PROBLEM RETURNING RESPONSE MESSAGE SOAP
Hi guys, I have problem with SOAP, I have this Web Service: <wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.