on 12-12-2007 11:49 AM
hi experts,
What could be wrong in ABAP Generated WSDL showing error when checked in SOAP tester?
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<soap-env:Fault>
<faultcode>soap-env:Client</faultcode>
<faultstring xml:lang="en">Deserialisation failed</faultstring>
<detail>
<n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates">
<MainName>/1BCDWB/WSS0071207135524390000</MainName>
<ProgName>/1BCDWB/WSS0071207135524390000</ProgName>
<Line>16</Line>
<Valid>X</Valid>
<DeserialisationFault>
good answers will be rewarded.
nikhil
no relevant answer, not even single tip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil,
Notice that (SAP) username & password are to be entered in correct case.
try to modify the WSDL URL to include sap-user and sap-password
...&sap-user=XXXYYz&sap-password=12345A1b
next thing u can try is to download (view the wsdl in a browser, right click, show source, save as...)the wsdl and save it to the same directory as your script, then modify the constructor to access that file...this should give you a hint if there's an error with your wsdl or only accessing the WSDL
Another possible error might arise from a non-resolvable service endpoint (i.e. the actual address being called when you invoke a service operation). If this has no fully qualified domain name or if that servername is not resolvable from the network segment where your ABAP script is being executed then no route to the service can befound.
Also keep in view that ABAP stack alters naming conventions depending on the version and test accordingly.
I hope this helps.
Regards,
Shibani
*Reward if helpful*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil Bos,
As per the information that you given, I have collected some data.
<soap:Env:Fault>
fault that might be returned in response to a request for the non-existent stock
The faultcode element is set to
SOAP-ENV:Client
to indicate that the client's request was incorrect. The faultstring element just contains a brief string of unmarked up text that can be used to more fully describe the problem to a human reader.
Try this Url, where check Ex. 2.19 along with the Fault description.
http://www.cafeconleche.org/books/xmljava/chapters/ch02s06.html
Hope this may help you.
Cheers'
Vinod V
*Reward, If found helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi vinod & shibani,
i have checked the wsdl in the browser, it shows without any error. And the soap fault shows that some deserialization problem, as you can see in the soap code mentioned in the first.
could you tell me about the soap action field specification for abap generated wsdls?
thanks for reply
nikhil bos
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.