I assume that you are using Axis C++ 1.5 release.
The need for SOAP Action for operations to succeed was dropped in the
post 1.5 code.
If you could try with a latest SVN checkout, you could see if the
problem id solved.
Thanks,
Samisa...
Liu, Richard wrote:
Hi,
I found out the problem that caused "Exception : Cannot deserialize
the requested element" when I use my own wsdl file.
It's caused by the "wsdlsoap:operation soapAction="add"/> line.
In the wsdl file provided in the demo directory, the above line is:
<wsdlsoap:operation soapAction="Calculator#add"/>
Which has a scope "Calculator#" in front of opertion "add".
However, If I generated my own wsdl file using the following Java2WSDL
tool command:
org.apache.axis.wsdl.Java2WSDL -o Calculator.wsdl
-l"http://localhost/axis/Calculator"; -n
"http://localhost/axis/Calculator"; -A OPERATION -S Calculator -w ALL
Calculator
The wsdl file I got has an wsdlsoap:operation soapAction line below:
<wsdlsoap:operation soapAction="add"/>
If I use this wsdl file to generate a C++ client side or java client
side code, it fails to invoke.
The C++ client got an error " Exception : Cannot deserialize the
requested element"
I have to manually add the "Calculator#" in front of "add" operation.
Can anybody told me how can I generate a workable wsdl file without
doing this manual change?
Thanks
Richard Liu
Software Engineer at Boeing
