Re: Client side objects not serializable

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Tue, 06 Sep 2005 13:00:28 -0700

I am a little confused. When you wrote your service, did you start from
Java classes or a WSDL?
I am assuming Java classes. In that case, the files generated from the
WSDL should only be used on the client side, not the server side. The
classes, as you have pointed out, are not interchangeable. If this does
not answer your question, please give a more detailed description of
what you are doing, including.

How the server side implementation was written, (e.g. imported a wsdl or
started from Java classes).
How the client was written (did you import the deployed WSDL etc)?

If the error you are getting on the server or on the client? Is it a
runtime error or a tool-time error?


Clinton wrote:

>I am having a problem doing an rpc from inside an EJB when using complexTypes.
>The complexType object created by the WSCompile tool no longer implements the
>Serializable interface and can thus not be sent to my client (because rmi can
>only send Serializable objects). My complexType only contains primitives, so is
>there any way of telling the WSCompile to create the client side complexType
>object as Serializable.
>Thanks in advance
>To unsubscribe, e-mail:
>For additional commands, e-mail:

 - Doug