I am trying to add Customer to a database (which is on the webservice side) by sending a Customer Object to the webservice. When the webservice receives the Customer Object it only has NULL values. So , none of the information (name, surname, address etc.) is filled in when the Webservice receives it.

Sending an integer to the Webservice works fine, receiving an array filled with Customer Objects from the Webservice works perfect. But sending a Customer object to the Webservice doesn't work properly.

I am really clueless right now how I am supposed to send an Object to a webservice. Is there anyone here who has experience with this kind of stuff. Help would be really appreciated. Thanks in advance.

Some web services might accept Java objects; most (AFAIK) don't. How would you communicate a Java object, for example, to a .Net web server?

Is this some particular web service I might know about (for example, Google)? Or is the web service in question one that you and your team have designed and implemented yourself? Or are you just curious?

Think of the web service itself as "an object", with various "method calls" that communicate with *your* object(s).

For whatever it's worth, this article might be of help:

http://www-128.ibm.com/developerwork...ry/ws-intwsdl/
http://www-128.ibm.com/developerwork...y/ws-intwsdl2/

Your .. PSM

It's a WebService written in Java, it is indeed designed by my team and we implemented it ourself yes. The WebService has a method called "addCustomer". The client will add a Customer using a GUI, when pressing the "Add Customer" button, the client will fill a Customer object with the given info from the GUI and this object will than be send to the WebService by using the client interface Classes generated from the WebService WSDL. The Customer Object is filled with data when at the client side, but when it is received on the server side all the values for a Customer (name, address etc.) are NULL.

Again, please take a look at the links:
Deploying Web services with WSDL: Part 1
Deploying Web services with WSDL Part 2: SOAP

Please pay particular attention to the part about "Compound Data types" in Part 2. This might be your best bet.

And please consider that you should What this means is that, even if you figure out how to pass an "object" (and I confess, I don't know how, or know if it's even possible or not), it's probably not a good idea. Because "objects" are (by definition) language- and platform- dependent, and introducing such dependencies defeats a large part of using web services in the first place!

IMHO .. PSM

I have already read that documentation, but thanks. About the objects, both my client and webservice are written in Java.

Thanks for the help.