That is not a WSDL, but a text description of a WSDL that makes it
difficult to see what the problem is. Your service provider should be
providing you an actual WSDL to work with.
If you have an actual WSDL (which will something like this[1]), you can
create a SOAP client[2] from it using either CXF or Metro and then
report back the problems, if any, you have. (When you say you
"[manually?] translated the WSDL to Java code" I'm not sure what you
did--CXF has a WSDL2Java tool for automatically doing that.
HTH,
Glen
[1] http://www.jroller.com/gmazza/entry/web_service_tutorial#WFstep4
[2] http://www.jroller.com/gmazza/entry/soap_client_tutorial
On 16.12.2010 05:28, meteora28 wrote:
Hello there,
here is my Problem:
I am implementing a web service from the following WSDL:
http://www.onvif.org/onvif/ver10/device/wsdl/devicemgmt.wsdl
I executed the method "GetDeviceInformation" with soapUI. There were no
problems.
The method has no parameters and some return values.
So I translated the WSDL to Java code. I wanted to execute the same methods
and the translated class shows me no return value. Instead of there are now
parameters to set, defined as these values which should be returned. Other
methods worked fine.
Is it possible that the WSDL wasn't correctly translated to Java code?
An other annotation: CXF (current version) was the only "framework" that was
able to translate the WSDL to Java code because the given has no service
element.
I hope that somebody knows a solution or a hint ;-)
Kind regards,
meteora28