[Logo]
Forums Register Login
WebServices - Passing the user defined object
Hi,

I have a webservice that exposes a method which takes an Object as a parameter. Hence, the client invoking this webservice can pass any type of object including user defined class objects.
e.g.: public String invokeMe(Ojbect obj);

From Client webservice: I am passing my user defined class object as a parameter to the exposed method.
Pitta obj = new Pitta(); // Pitta is the name of a class.
e.g.: String result = invokeMe(obj);

When invoked on stub from client side, it gives me the exception saying that 'Pitta' needs to have a deserializer.

I have even tried by extending 'Serializer' interface to class 'Pitta' but it was of no use. I understand that all the objects passed over the SOAP protocol need to be capapble of serializing and deserializing.

My Question: How do we pass the different objects over SOAP Protocol?

Thanks for your time.

Regards,
Pitta.
Have a look at this article (Using Complex Types in Web Services) by Balaji Loganathan explaining how to pass complex objects to webservice
JaiKiran,

Thanks for your reply. But my question was passing the complex object (user defined object) from Client Side when WebService exposes the method of OBJECT type as a parameter. I am getting exception while passing the user defined object (as mentioned in my previous posting).

Regards,
Pitta.
Can anyone please respond to my question below?

Regards,
Pitta.
 
Thanks for your reply. But my question was passing the complex object (user defined object) from Client Side when WebService exposes the method of OBJECT type as a parameter.


Why would you expect this to work?

How can the web service possibly know in advance about all the possible user defined objects?

Bill
 
Originally posted by Srinivas Pitta:
my question was passing the complex object (user defined object) from Client Side when WebService exposes the method of OBJECT type as a parameter.


I don't think this will work. Objects don't have deserializers, so you'd need to cast it into something that was known to support Serializable. And if you're going to do that, you might as well just declare your parameter as a Serializable (at the very least).

What exactly is it you're trying to do? Why would you want to accept unknown objects into your service?
Wink, wink, nudge, nudge, say no more ... https://richsoil.com/cards



All times above are in ranch (not your local) time.
The current ranch time is
Nov 22, 2017 15:05:32.