Generating and using client code from wsdl file with wsimport

[Miklos Szeles]

Hi,
I'm trying to generate the client code of a web service based on a wsdl file. This web service is used for communicating with IP cameras. The WSDL file is available here:
http://www.onvif.org/onvif/ver10/device/wsdl/devicemgmt.wsdl

My first problem is that wsimport says that the wsdl file does not contain any services. To solve this problem, I've downloaded the wsdl file and added the following lines:

		<wsdl:service name="DeviceService">
			<wsdl:port name="DevicePort" binding="tds:DeviceBinding">
				<soap:address location="http://localhost/onvif/device_service"/>
			</wsdl:port>
		</wsdl:service>

After this wsimport says the following:

[WARNING] Service "DeviceService" does not contain any usable ports. try running wsimport with -extension switch.
  line 3720 of file:/D:/Share/ONVIF/wsimport/wsdl/devicemgmt.wsdl

So I used -extension and I was able to generate the source files.
Is this okay that I use a "dummy" service location just for generating the source codes?
Is it okay to use the -extension option, or should I define a service differently in the wsdl?

Next problem occurs when I would like to use the generated code. Actually I don't really know how to use it. I have a generated DeviceService class, so I try to instantiate it:

DeviceService service = new DeviceService(
new URL("http://www.onvif.org/onvif/ver10/device/wsdl/devicemgmt.wsdl"), 
new QName("http://192.168.4.148/onvif/device_service"));

In case I use the wsdl location from the internet, then I get an error that the wsdl does not contain a service definition, so I try to use the modified wsdl file

DeviceService service = new DeviceService(
new URL("file:///d|/Share/ONVIF/wsimport/wsdl/devicemgmt.wsdl"), 
new QName("http://192.168.4.148/onvif/device_service"));

In that case I receive the following error:

javax.xml.ws.WebServiceException: http://192.168.4.148/onvif/device_service is not a valid service. Valid services are: {http://www.onvif.org/ver10/device/wsdl}DeviceService

So I'm stuck at this point. Any idea what should I do differently to make this thing work?
I also don't really understand why do I have to specify the wsdl url again, since I generated the code from that wsdl.
Thanks in advance.

[Ivan Krizsan]

Hi!
First of all, without a <service> and <port> element, the WSDL is incomplete. Is this perhaps a WSDL that is imported by another WSDL that in turn specifies the missing elements?
If the WSDL is incomplete, then it is something that should be taken care of by the service provider.
With an incomplete, or invalid, WSDL it becomes much more difficult, if not impossible, to develop a working client for the service.

Second, regarding creating webservice clients, the approach depends a little on the IDE you use:
Here is a tutorial for NetBeans: http://netbeans.org/kb/docs/websvc/client.html
For Eclipse, take a look in section 4.9 in the following e-book (all examples in the book were developed using Eclipse): http://www.slideshare.net/krizsan/scdjws-5-study-notes-3085287
Best wishes!

[Miklos Szeles]

Thanks Ivan. Actually I found the answer for my problem in one of your posts. So the solution is to use the default constructor for the service and change the endpoint

((BindingProvider)proxy).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://new/endpointaddress"); 

I think the reason why there is no service in the wsdl file because that site does not offer any service. It is a standard for IP cameras, so the cameras itself will offer the service not this site. Is this makes sense?

I've run into another issue unfortunately. I can make calls which requires no authentication, but I don't know how can I insert UsernameToken authentication (what is required here) into the generated classes. Any idea on that issue?
Thanks.

[Ivan Krizsan]

Hi!
I would not aim at modifying the generated classes, but rather modify a local copy of the WSDL by adding the appropriate WS-Policy elements and then generating the client artifacts.
For an example, see this article: http://www.ibm.com/developerworks/java/library/j-jws10/index.html
Best wishes!

[Miklos Szeles]

Thanks. I did not want to modify the generated classes, I just thought that maybe it is possible to add the required security part to the messages.
Does this mean that it is not possible to make UsernameToken authentication only with the JDK 1.6 built in capabilities, but I have to use a 3rd party solution for this like the mentioned Metro or Apache Axis2 or ...?

[Jason Majchrzak]

Miklos,

I am venturing down the same road that you came from. Can you share your experience? How did you manage to resolve adding the service to the ONVIF WSDL document? Also, were you able to pass user name, password, nonce and request time? I've been able to use wsimport to generate the required classes, but I don't have a "DeviceService.java" file generated even when I've modified a local copy of devicemgmt.wsdl.

Thanks,
Jason

[Miklos Szeles]

Hi Jason,
I suspended working on this issue, so I made no further progress regarding this.
Best regards,
Miklós

[Jason Majchrzak]

Thank you for an update Miklos!

[Ido Shlomo]

You were so close!
After banging my head with this for a few days I finally found the fix!

String camIp = "192.168.4.148";

// Start off, just loading the document with the DeviceService addition you made earlier
URL url = new URL("file:///d|/Share/ONVIF/wsimport/wsdl/devicemgmt.wsdl");
QName qname = new QName("http://www.onvif.org/ver10/device/wsdl", "DeviceService");
Service service = Service.create(url, qname);
Device device = service.getPort(Device.class);

// Now this is where the magic happens!
((BindingProvider)device).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY ,  
	"http://"+camIp+"/onvif/device_service"); 

// Test it !
Holder<String> manufacturer = new Holder<String>();
Holder<String> model = new Holder<String>();
Holder<String> firmwareVersion = new Holder<String>();
Holder<String> serialNumber = new Holder<String>();
Holder<String> hardwareId = new Holder<String>();
device.getDeviceInformation(manufacturer, model, firmwareVersion, serialNumber, hardwareId);
System.out.println(manufacturer.value);
System.out.println(model.value);
System.out.println(firmwareVersion.value);
System.out.println(serialNumber.value);
System.out.println(hardwareId.value);

/Edit
It works for devices that don't require authentication. I'm still stuck with authenticating when needed.

[Ido Shlomo]

I finally solved it:

Start off by browsing into the Axis camera's web interface:

Open your browser
Open the Axis camera's web interface
Go to Setup -> System Options -> Security -> ONVIF
Add a user!

Now for the code part.
You start off by reading the server's clock:

SystemDateTime systemDateAndTime = device.getSystemDateAndTime();
clientTime = System.currentTimeMillis;
	    
DateTime utcDateTime = systemDateAndTime.getUTCDateTime();
org.onvif.ver10.schema.Date date = utcDateTime.getDate();
Time time = utcDateTime.getTime();
Calendar c = new GregorianCalendar(utc);
c.set(date.getYear(), date.getMonth()-1, date.getDay(), time.getHour(), time.getMinute(), time.getSecond());
serverTime = c.getTimeInMillis();

Then, you create an authentication header.
For that you need to bind a handler:

	    BindingProvider bindingProvider = (BindingProvider)device;

	    final Binding binding = bindingProvider.getBinding();
		List<Handler> handlerList = binding.getHandlerChain();
	    if (handlerList == null)
	        handlerList = new ArrayList<Handler>();

	    handlerList.add(new SecurityHandler());
	    binding.setHandlerChain(handlerList);

Implement the handler

    private static TimeZone utc = TimeZone.getTimeZone("UTC");
	private static SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss.SSS'Z'");

	static {
		sdf.setTimeZone(utc);
	}

	private static long serverTime = 0;
	private static long clientTime = 0;

	// calculate diff between my time and the camera's time
	private static String localToGmtTimestamp() {
    		return sdf.format(new Date(System.currentTimeMillis()-clientTime+serverTime));
	}

	
	public static final class SecurityHandler implements SOAPHandler<SOAPMessageContext> {

	    @Override
	    public boolean handleMessage(final SOAPMessageContext msgCtx) {

	        // Indicator telling us which direction this message is going in
	        final Boolean outInd = (Boolean) msgCtx.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);

	        // Handler must only add security headers to outbound messages
	        if (outInd.booleanValue() && clientTime!=0) {
	            try {
	            	
	            	String timestamp = localToGmtTimestamp();
	            	String user = ...;
	            	String pass = ...;
	            	byte[] nonceBytes = new byte[16]; 
	            	for (int i=0 ; i<16 ; ++i)
	            		nonceBytes[i] = (byte)(Math.random()*256-128);

	            	String dig=calculatePasswordDigest(nonceBytes, timestamp, pass);

	            	SOAPEnvelope envelope = msgCtx.getMessage().getSOAPPart().getEnvelope();
	                SOAPHeader header = envelope.getHeader();
	                if (header == null)
	                    header = envelope.addHeader();
	                
	            	SOAPElement security =
	            	header.addChildElement("Security", "wsse", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd");

	            	SOAPElement usernameToken =
	            	security.addChildElement("UsernameToken", "wsse");
	            	
	            	SOAPElement username =
	            	usernameToken.addChildElement("Username", "wsse");
	            	username.addTextNode(user);

	            	SOAPElement password =
	            	usernameToken.addChildElement("Password", "wsse");
	            	password.setAttribute("Type", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest");
	            	password.addTextNode(dig);

	            	SOAPElement nonce =
	            	usernameToken.addChildElement("Nonce", "wsse");
	            	nonce.setAttribute("EncodingType", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary");
	            	nonce.addTextNode(Base64.encode(nonceBytes));

	            	SOAPElement created = usernameToken.addChildElement("Created", "wsu", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd");
	            	created.addTextNode(timestamp);

	            } catch (final Exception e) {
	            	e.printStackTrace();
	                return false;
	            }
	        }
	        return true;
	    }

	    // Other required methods on interface need no guts

	    @Override
		public boolean handleFault(SOAPMessageContext context) {
			// TODO Auto-generated method stub
			return false;
		}

		@Override
		public void close(MessageContext context) {
			// TODO Auto-generated method stub
			
		}

		@Override
		public Set<QName> getHeaders() {
			// TODO Auto-generated method stub
			return null;
		}
	}

And there you have it.

[Ido Shlomo]

An important thing I've discovered about Axis cameras:
Once you set the initial root password using the web interface, the ONVIF interface will not allow access.
You must reset the camera to its factory defaults in order to use the ONVIF interface without credentials.
You should now be able to initialize the root password and ONVIF passwords via the ONVIF interface.
If you did, however initialize the camera's root password via the web interface, you should also manually add an ONVIF user as explained above.
I would like to thank this blessed behavior for wasting my time.

[Ido Shlomo]

Looks like I forgot to add the implementation of the message digest creation:

	private static String calculatePasswordDigest(byte[] nonceBytes, String created, String password) {
        String encoded = null;
        try {
            MessageDigest md = MessageDigest.getInstance( "SHA1" );
            md.reset();
            md.update( nonceBytes );
            md.update( created.getBytes() );
            md.update( password.getBytes() );
            byte[] encodedPassword = md.digest();
            encoded = Base64.encode(encodedPassword);
        } catch (NoSuchAlgorithmException ex) {
        }

        return encoded;
    }

[Sarfraz Ahmed]

I tried it using C. Because I am writing my API in C. But it can not authenticate me. My question is am I making three parameters right (Random number, Time String and password Digest). I verify my SHA1 Output on this site. http://hash.online-convert.com/sha1-generator

unsigned int nonce_int = 0, i = 0;
  time_t utcTime = 0;
  struct tm *timeInfo = NULL;
  char sha1_input[100] = { 0 };
  SHA1Context sha = { 0 };  

  nonce_int = GetRandomNumber();
  encode_base64(sizeof(nonce_int), (char*)&nonce_int, nonceLen, noncestr);

  utcTime = time(NULL);
  timeInfo = localtime(&utcTime);
  strftime(timestr, timeLen, "%Y-%m-%dT%H:%M:%SZ", timeInfo);
  printf("\nTime in String Format = %s", timestr);
  
  sprintf(sha1_input, "%d%s%s", nonce_int, timestr, password);
  
  SHA1Reset(&sha);
  SHA1Input(&sha, (const unsigned char*)sha1_input, strlen(sha1_input));

  if(!SHA1Result(&sha))
  {
    printf("\nERROR-- could not compute message digest");
  }
  else
  {
    int i = 0;
    memset(sha1_input, 0x00, sizeof(sha1_input));
    
    sprintf(sha1_input, "%X%X%X%X%X", sha.Message_Digest[0], sha.Message_Digest[1],
      sha.Message_Digest[2], sha.Message_Digest[3], sha.Message_Digest[4]);

    for(i = 0; i < 5; i++)
    {
      sha.Message_Digest[i] = ntohl(sha.Message_Digest[i]);
    }
     
    printf("\nSHA1 Digest = %s", sha1_input);
    encode_base64(sizeof(sha.Message_Digest), (unsigned char*)sha.Message_Digest, digestLen, digeststr);
    printf("\nSHA1 Digest Base64 Encoded = %s", digeststr);
   
  }

  return 0;

[Ido Shlomo]

nonce is an array of 16 bytes, not an int.
the byte[16] none may contain zeros, so use memcpy, instead of sprintf

[Sarfraz Ahmed]

I changed my code as follow. But still giving same Error. The returned HTTP Error code is 500. I changed the nonce for every request for testing purposes.

unsigned int nonce_int = 0, i = 0;
  time_t utcTime = 0;
  struct tm *timeInfo = NULL;
  char sha1_input[100] = { 0 };
  SHA1Context sha = { 0 };
  unsigned char nonce[] = "1234567892133613";

  encode_base64(strlen(nonce), nonce, nonceLen, noncestr);
  utcTime = time(NULL);
  timeInfo = localtime(&utcTime);
  strftime(timestr, timeLen, "%Y-%m-%dT%H:%M:%SZ", timeInfo);
  sprintf(sha1_input, "%s%s%s", nonce, timestr, password);
  
  SHA1Reset(&sha);
  SHA1Input(&sha, (const unsigned char*)sha1_input, strlen(sha1_input));

  if(!SHA1Result(&sha))
  {
    printf("\nERROR-- could not compute message digest");
  }
  else
  {
    memset(sha1_input, 0x00, sizeof(sha1_input));
    for(i = 0; i < 5; i++)
    {
      sha.Message_Digest[i] = ntohl(sha.Message_Digest[i]);
    }
    encode_base64(sizeof(sha.Message_Digest), (unsigned char*)sha.Message_Digest, digestLen, digeststr);
  }

  return 0;

[Ido Shlomo]

1. Is your clock synchronized with the device you're trying to connect to?

2. I've tried using the nonce you've posted and got the following results:

Input
nonce str: 1234567892133613
time str: 1970-01-11T21:39:42.208Z
pass str: 123456

In bytes:
nonce bytes: [49, 50, 51, 52, 53, 54, 55, 56, 57, 50, 49, 51, 51, 54, 49, 51]
time bytes: [49, 57, 55, 48, 45, 48, 49, 45, 49, 49, 84, 50, 49, 58, 51, 57, 58, 52, 50, 46, 50, 48, 56, 90]
pass bytes: [49, 50, 51, 52, 53, 54]

Result:
digest str: TiWxOU9wmwlMQlIx3a856HpQYAk=
digest bytes: [84, 105, 87, 120, 79, 85, 57, 119, 109, 119, 108, 77, 81, 108, 73, 120, 51, 97, 56, 53, 54, 72, 112, 81, 89, 65, 107, 61]

Please make sure you get the same result when using this exact input.

[Sarfraz Ahmed]

I tried the Inputs and my Outputs Matches with your ones. I am attaching my whole code. May be at some other place I am making mistake. That I am unable to detect.

I create my headers in this function.

int authenticate(char *username, char *password, char *timestr, int timeLen, 
                 char *noncestr, int nonceLen, char *digeststr, int digestLen)
{   
  unsigned int i = 0;
  time_t utcTime = 0;
  struct tm *timeInfo = NULL;
  char sha1_input[100] = { 0 };
  SHA1Context sha = { 0 };
  unsigned char nonce[] = "12345l7892133625";
   
  encode_base64(sizeof(nonce), nonce, nonceLen, noncestr);
  utcTime = time(NULL);
  timeInfo = localtime(&utcTime);
  strftime(timestr, timeLen, "%Y-%m-%dT%H:%M:%SZ", timeInfo);
  
  sprintf(sha1_input, "%s%s%s", nonce, timestr, password);
  
  SHA1Reset(&sha);
  SHA1Input(&sha, (const unsigned char*)sha1_input, strlen(sha1_input));

  if(!SHA1Result(&sha))
  {
    printf("\nERROR-- could not compute message digest");
  }
  else
  {
    for(i = 0; i < 5; i++)
    {
      sha.Message_Digest[i] = ntohl(sha.Message_Digest[i]);
    }
    encode_base64(sizeof(sha.Message_Digest), (unsigned char*)sha.Message_Digest, digestLen, digeststr);
  }

  return 0;
}

and this is how I am sending SOAP request.

int authenticate_user()
{
  char time_char[30] = { 0 };
  char base64EncDigest[200] = { 0 };
  char username[] = "root";
  char password[] = "camera";
  char nonce_char[100] = { 0 };
  HttpResponse_t res = { 0 };
  HttpReq_t req = { 0 };
  char headers[2048] = { 0 };
  char postData[2048] = { 0 };
  char auth[512] = { 0 };
  int rval = 0;
  char *url = "/onvif/device_service";//"/onvif/ptz_service";
  
  req.sock = TcpClientSocket(ip, port, 500, 1000, 2000);
  if(req.sock == -1)
  {    
    printf("%s, Unable to connect to '%s:%d'", ip, port);
    return -1;
  }

  req.url = url;
  req.hdrs = headers;
  req.postData = postData;

  snprintf(auth, sizeof(auth)-1, "%s:%d", ip, port); 
  http_add_header(headers, sizeof(headers), "Host", auth);
  http_add_header(headers, sizeof(headers), "Content-Type", "application/soap+xml; charset=utf-8");
  http_add_header(headers, sizeof(headers), "Accept-Encoding", "*/*");

  authenticate(username, password, time_char, sizeof(time_char), 
    nonce_char, sizeof(nonce_char), base64EncDigest, sizeof(base64EncDigest));

  snprintf(postData, sizeof(postData),
      "<?xml version=\"1.0\" encoding=\"utf-8\"?>"
      "<soap:Envelope  xmlns:soap=\"http://www.w3.org/2003/05/soap-envelope\" " 
			"xmlns:SOAP-ENC=\"http://www.w3.org/2003/05/soap-encoding\" " 
			"xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" " 
			"xmlns:xs=\"http://www.w3.org/2001/XMLSchema\" " 
			"xmlns:c14n=\"http://www.w3.org/2001/10/xml-exc-c14n#\" " 
			"xmlns:ds=\"http://www.w3.org/2000/09/xmldsig#\" " 
			"xmlns:wsa=\"http://www.w3.org/2005/08/addressing\" " 
			"xmlns:wstop=\"http://docs.oasis-open.org/wsrf/r-2\" " 
			"xmlns:xm=\"http://www.w3.org/2005/05/xmlmime\" " 
			"xmlns:tt=\"http://www.onvif.org/ver10/schema\" " 
			"xmlns:wsbf2=\"http://docs.oasis-open.org/wsrf/bf-2\" " 
			"xmlns:wst1=\"http://docs.oasis-open.org/wsn/t-1\" " 
			"xmlns:wsnt=\"http://docs.oasis-open.org/wsn/b-2\" " 
			"xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd\" " 
			"xmlns:wsu=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd\" " 
			"xmlns:tds=\"http://www.onvif.org/ver10/device/wsdl\" " 
			"xmlns:timg=\"http://www.onvif.org/ver10/imaging/wsdl\" " 
			"xmlns:tptz=\"http://www.onvif.org/ver10/ptz/wsdl\" " 
			"xmlns:trt=\"http://www.onvif.org/ver10/media/wsdl\">"				
	    "<soap:Header>"
		  "<wsse:Security xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd\" " 
			"xmlns:wsu=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd\">"
			"<wsse:UsernameToken>"
			"<wsse:Username>%s</wsse:Username>"
			"<wsse:Password Type=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest\">"
			"%s</wsse:Password>"
			"<wsse:Nonce>%s</wsse:Nonce>"
			"<wsu:Created>%s</wsu:Created>"
			"</wsse:UsernameToken></wsse:Security>"
	    "</soap:Header>"
	    "<soap:Body>"
		  "<tds:GetDeviceInformation/>"
	    "</soap:Body>"
      "</soap:Envelope>",
      username, base64EncDigest, nonce_char, time_char);

  
  rval = http_serv_post(&req, &res);
  if(res.statusCode != 200)
  {
    printf("\nCan not get Device Information");
  }
  SockClose(&req.sock);
  http_reset_response(&res);
  

  return 0;
}

Thanks

[Ido Shlomo]

By the username, I'm guessing that you are using an axis camera.
You need to create a user specific for ONVIF in the cameras web interface.

You should also try to read the camera's current time, and use that for authentication instead of your local time.
See my example above

[Sarfraz Ahmed]

Its a canon camera, VB-M40. I tried to read the time value from the camera and then use that string to authenticate. But the Error response was same.

[Jane Chu]

Hello,

I am very new on the tech of web services.

Somehow, I got a sample code online which is very similar to the one here. The wsdl and xsd files are downloaded from onvif. The original code works well. (I have got the device info, server time)

Now, I want to make more service requests. For example, getServices. I added the following 2 lines in:

boolean includeCapability = true;
device.getServices(includeCapability);

but, the response link seemed fixed to the one pointing to device info. Here is the error message:

unexpected XML tag. expected: {http://www.onvif.org/ver10/device/wsdl}GetServicesResponse but found: {http://www.onvif.org/ver10/device/wsdl}GetWsdlUrlResponse

Does anyone could help me out? Any help would be highly appreciated.

[Ido Shlomo]

Yeah, I've cleaned it up and reposted this solution on stack overflow http://stackoverflow.com/questions/8798419/build-soap-web-service-client-using-wsdl-documents-in-eclipse/10394687

It looks that either the device you're communicating with returns the wrong class, or that it tries to return an error.
I'd suggest using wireshark to read the traffic directly and look at the xml that you end up sending and the xml you receive back from the device.
It's usually readable enough to help you understand what went wrong.

[Jane Chu]

Yeah, It's you! I tried looking for you for several days! I am glad to meet you here!
Thank you very much for your reply. I will try wireshark. I did exactly as you suggested in the comments right after that "URL url" line. Your comments were pretty straight forward and easy to follow. In this case, do you have any idea where might go wrong? Thank you again!

[Jane Chu]

You are right. The traffic I caught by wireshark shows that the device got the request, but the "Connection: close". Then it went to somewhere else. Thank you very much again!

[Miklos Szeles]

Thanks to Ivan's and Ido's advices I was able to authenticate the user and execute different calls from the device management service. So thank you very much for that.
I've started to experiment with the Media service but I wasn't able to get it work.
I'm instantiating the service with the following code:

MediaService service = new MediaService();
media = service.getMediaPort();
	((BindingProvider)fMedia).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, 
	"http://" + address + "/onvif/device_service");

I also instantiate a DeviceService to get the date and time for the authentication. Using that information I create a SecurityHandler and "attach" it to the service according to the previous posts.
This works nicely for the Device calls, but whenever I call media.getProfiles() I receive the following exception:

com.sun.xml.internal.ws.protocol.soap.VersionMismatchException: Couldn't create SOAP message. 
	Expecting Envelope in namespace http://www.w3.org/2003/05/soap-envelope, 
	but got http://schemas.xmlsoap.org/soap/envelope/ 

Using wireshark I can even see the answer was sent by the camera (I've pasted the request and the response at the and of my post).
I tried to google for the exception but I haven't found the solution yet. What can be the problem?

The outgoing message is :
POST /onvif/device_service HTTP/1.1 Content-type: application/soap+xml;charset="utf-8";action="http://www.onvif.org/ver10/media/wsdl/GetProfiles" Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 User-Agent: JAX-WS RI 2.1.6 in JDK 6 Host: 192.168.5.56 Connection: keep-alive Content-Length: 1285 <?xml version="1.0" ?> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"> <S:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>admin</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"> oeaDyodtCn6wLYimATPUympxuBU=</wsse:Password> <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"> oBzcF128D60eh+q29qNj6A==</wsse:Nonce> <wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> 2012-12-12T19:07:35.675Z</wsu:Created> </wsse:UsernameToken> </wsse:Security> </S:Header> <S:Body> <ns10:GetProfiles xmlns:ns10="http://www.onvif.org/ver10/media/wsdl" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns4="http://docs.oasis-open.org/wsrf/bf-2" xmlns:ns5="http://www.w3.org/2005/08/addressing" xmlns:ns6="http://docs.oasis-open.org/wsn/b-2" xmlns:ns7="http://docs.oasis-open.org/wsn/t-1" xmlns:ns8="http://www.onvif.org/ver10/schema" xmlns:ns9="http://www.w3.org/2004/08/xop/include" xmlns:xmime="http://www.w3.org/2005/05/xmlmime"></ns10:GetProfiles> </S:Body> </S:Envelope>

The response is:
HTTP/1.1 200 OK Server: gSOAP/2.8 Content-Type: application/soap+xml; charset=utf-8 Content-Length: 5403 Connection: close <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xmime="http://tempuri.org/xmime.xsd" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:wsrf-r="http://docs.oasis-open.org/wsrf/r-2" xmlns:tan1="http://www.onvif.org/ver20/analytics/wsdl/RuleEngineBinding" xmlns:tan2="http://www.onvif.org/ver20/analytics/wsdl/AnalyticsEngineBinding" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:tev1="http://www.onvif.org/ver10/events/wsdl/PullPointSubscriptionBinding" xmlns:tev2="http://www.onvif.org/ver10/events/wsdl/EventBinding" xmlns:tev3="http://www.onvif.org/ver10/events/wsdl/SubscriptionManagerBinding" xmlns:tev4="http://www.onvif.org/ver10/events/wsdl/NotificationProducerBinding" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tnsht="http://www.onvifplus.org/event/topics"> <SOAP-ENV:Header></SOAP-ENV:Header> <SOAP-ENV:Body> <trt:GetProfilesResponse> <trt:Profiles fixed="true" token="Profile1"> <tt:Name>Profile1</tt:Name> <tt:VideoSourceConfiguration token="1"> <tt:Name>video_source1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:SourceToken>1</tt:SourceToken> <tt:Bounds height="1080" width="1920" y="0" x="0"></tt:Bounds> </tt:VideoSourceConfiguration> <tt:AudioSourceConfiguration token="1"> <tt:Name>audio_source1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:SourceToken>1</tt:SourceToken> </tt:AudioSourceConfiguration> <tt:VideoEncoderConfiguration token="1"> <tt:Name>video_encoder1</tt:Name> <tt:UseCount>1</tt:UseCount> <tt:Encoding>H264</tt:Encoding> <tt:Resolution> <tt:Width>640</tt:Width> <tt:Height>480</tt:Height> </tt:Resolution> <tt:Quality>50</tt:Quality> <tt:RateControl> <tt:FrameRateLimit>25</tt:FrameRateLimit> <tt:EncodingInterval>0</tt:EncodingInterval> <tt:BitrateLimit>4000</tt:BitrateLimit> </tt:RateControl> <tt:H264> <tt:GovLength>25</tt:GovLength> <tt:H264Profile>Baseline</tt:H264Profile> </tt:H264> <tt:Multicast> <tt:Address> <tt:Type>IPv4</tt:Type> <tt:IPv4Address>231.1.128.20</tt:IPv4Address> </tt:Address> <tt:Port>40000</tt:Port> <tt:TTL>1</tt:TTL> <tt:AutoStart>false</tt:AutoStart> </tt:Multicast> <tt:SessionTimeout>PT0S</tt:SessionTimeout> </tt:VideoEncoderConfiguration> <tt:AudioEncoderConfiguration token="1"> <tt:Name>audio_encoder1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:Encoding>G711</tt:Encoding> <tt:Bitrate>64</tt:Bitrate> <tt:SampleRate>8</tt:SampleRate> <tt:Multicast> <tt:Address> <tt:Type>IPv4</tt:Type> <tt:IPv4Address>231.1.128.20</tt:IPv4Address> </tt:Address> <tt:Port>40002</tt:Port> <tt:TTL>1</tt:TTL> <tt:AutoStart>false</tt:AutoStart> </tt:Multicast> <tt:SessionTimeout>PT0S</tt:SessionTimeout> </tt:AudioEncoderConfiguration> <tt:Extension></tt:Extension> </trt:Profiles> <trt:Profiles fixed="true" token="Profile2"> <tt:Name>Profile2</tt:Name> <tt:VideoSourceConfiguration token="1"> <tt:Name>video_source1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:SourceToken>1</tt:SourceToken> <tt:Bounds height="1080" width="1920" y="0" x="0"></tt:Bounds> </tt:VideoSourceConfiguration> <tt:AudioSourceConfiguration token="1"> <tt:Name>audio_source1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:SourceToken>1</tt:SourceToken> </tt:AudioSourceConfiguration> <tt:VideoEncoderConfiguration token="2"> <tt:Name>video_encoder2</tt:Name> <tt:UseCount>1</tt:UseCount> <tt:Encoding>JPEG</tt:Encoding> <tt:Resolution> <tt:Width>640</tt:Width> <tt:Height>480</tt:Height> </tt:Resolution> <tt:Quality>50</tt:Quality> <tt:RateControl> <tt:FrameRateLimit>25</tt:FrameRateLimit> <tt:EncodingInterval>0</tt:EncodingInterval> <tt:BitrateLimit>0</tt:BitrateLimit> </tt:RateControl> <tt:Multicast> <tt:Address> <tt:Type>IPv4</tt:Type> <tt:IPv4Address>231.1.128.21</tt:IPv4Address> </tt:Address> <tt:Port>40006</tt:Port> <tt:TTL>1</tt:TTL> <tt:AutoStart>false</tt:AutoStart> </tt:Multicast> <tt:SessionTimeout>PT0S</tt:SessionTimeout> </tt:VideoEncoderConfiguration> <tt:AudioEncoderConfiguration token="1"> <tt:Name>audio_encoder1</tt:Name> <tt:UseCount>2</tt:UseCount> <tt:Encoding>G711</tt:Encoding> <tt:Bitrate>64</tt:Bitrate> <tt:SampleRate>8</tt:SampleRate> <tt:Multicast> <tt:Address> <tt:Type>IPv4</tt:Type> <tt:IPv4Address>231.1.128.20</tt:IPv4Address> </tt:Address> <tt:Port>40002</tt:Port> <tt:TTL>1</tt:TTL> <tt:AutoStart>false</tt:AutoStart> </tt:Multicast> <tt:SessionTimeout>PT0S</tt:SessionTimeout> </tt:AudioEncoderConfiguration> <tt:Extension></tt:Extension> </trt:Profiles> </trt:GetProfilesResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

[Ido Shlomo]

You might need to find a different version of the wsdl file. You used soap 1.2 and the device requires you to use soap 1.1

[Miklos Szeles]

Are you sure? For me it looks like the camera has no problem with this, since it sends the answer. The Java code generates this exception when processing the answer. According to the comment read on the ONVIF forum:

Generally the ONVIF working groups and Technical Committee take utmost care to ensure interoperability within the same version set by the namespace. So you can safely use the latest wsdl files for your implementation. Newer functionality is defined optional and bound to capabilities so that a client can easily find out whether a device supports it.

So based on this I should be able to use the latest wsdls only.

UPDATE:
I've downloaded and used the old WSDL files, but I receive the same error message.

[Miklos Szeles]

Further analyzing the problem I found the source of the problem (but I still can't find the solution).

It looks like the camera can send SOAP 1.2 messages, in case if the request is SOAP 1.2(I've used the test tool to check this).
Despite of the fact that the code generates a correct link for the Envelop namespace at the beginning:

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">  

It also contains the SOAP 1.1 Envelop namespace URL:

<ns10:GetProfiles xmlns:ns10="http://www.onvif.org/ver10/media/wsdl"  
            xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"

In case I send a message without the second envelop namespace, the camera response in SOAP 1.2 format.

So the problem is reduced back to the following:
Why the generated code do this? How can I convince wsimport to generate the correct Envelop?
I use the -extension with wsimport.>

[Ido Shlomo]

I think that the problem is in the fake service we added to the wsdl
It should be soap12:address instead of soap:address

[Miklos Szeles]

Unfortunately that did not help.
I don't know what would be the "correct" solution - I hope somebody will answer it in the future - but I found a workaround which works:
After generating the source files, I've replaced all
http://schemas.xmlsoap.org/soap/envelope
with
http://www.w3.org/2003/05/soap-envelope

That solves the issue.