Hello,
a customer has to integrate a webservice client to call an SAP WebService. But the provided wsdl file can't be analyzed by bprowsdldoc. What WSDL standard does bprowsdldoc support, so that the customer can require a standard definition from SAP partners?
The current error on bprowsdldoc is:
C:\Xc\Sample_wsdl>bprowsdldoc 0010000157_vag.TestWebservice.wsdl Error loading WSDL document 0010000157_vag.TestWebservice.wsdl : Cannot resolve reference to : GetWhsOnStockforItem{[null]} for part body infile:C:/Xc/Sample_wsdl/0010000157_vag.TestWebservice.wsdl line 51 column 58 (11748)
Thank you
Peter
Hello,
a customer has to integrate a webservice client to call an SAP WebService. But the provided wsdl file can't be analyzed by bprowsdldoc. What WSDL standard does bprowsdldoc support, so that the customer can require a standard definition from SAP partners?
The current error on bprowsdldoc is:
C:\Xc\Sample_wsdl>bprowsdldoc 0010000157_vag.TestWebservice.wsdl Error loading WSDL document 0010000157_vag.TestWebservice.wsdl : Cannot resolve reference to : GetWhsOnStockforItem{[null]} for part body infile:C:/Xc/Sample_wsdl/0010000157_vag.TestWebservice.wsdl line 51 column 58 (11748)
Thank you
Peter
Flag this post as spam/abuse.
It is 11.3.2.
In 11.3.2, we support both SOAP 1.1 and SOAP 1.2
Hello,
I know this too. But does de bprowsdldoc support the WSDL 1.1 or 2.0 standard?
bprowsdldoc doesn't support WSDL 1.2; only WSDL 1.1 is supported. If the SAP webservice can only provide WSDL 2.2 , the customer can convert it to WSDL 1.1 using W3C tool bellow:
The page shows a conversion from WSDL 1.1 to WSDL 2.0. But interesting is the result at the last row. So the outcome is not valid.
Au contraire to this, why can SOAPUI analyze the original wsdl document and create a sample request out of this?
<xs:documentation>As the element 'StockInformation' contains multiple child-elements with the same name, it is assumed that it contains a database-table dump with similar rows. Thus, only one of those multiple elements with the biggest sub-element count has been dumped to this schema, assuming to be the superset of such a row, allowing a cardinality from zero til unbounded, making all of the sub-elements optional. Note that it is necessary for this approach being accurate that at least one of those ro
Using org.apache.xerces.parsers.SAXParser
Exception net.sf.saxon.trans.XPathException: Namespace URI is an empty string
Namespace URI is an empty string
Sorry I had it backward-W3C doesn’t have WSDL 2.2 to WSDL 1.1 converter. Only WSDL 1.1 to WSDL 1.2