You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Xavier Toth <tx...@gmail.com> on 2005/11/04 21:45:42 UTC
client serialization without wsdl2java generated type
I have a situation where I'm running a service and a client of the same
service in one vm. So I've deleted the wsdl2java generated type (the type of
the argument to a service method) because I have a jar with the actual type
already. The argument type contains a String and a byte[] and the byte[] is
the part that isn't getting to the service correctly. I'm not sure if it is
a serialization or deserialization problem. I've added the typemapping from
my server side wsdd to my client wsdd but that didn't fix things. Any ideas?
Re: client serialization without wsdl2java generated type
Posted by Xavier Toth <tx...@gmail.com>.
They talk to other boxes not to each other. Anyway I see that I have to
register the types with the call object since I'm not using the wsdl2java
generated classes.
On 11/7/05, Anne Thomas Manes <at...@gmail.com> wrote:
>
> If you have two Java applications running in the same VM, why are you
> using SOAP to communicate with them?
>
> Anne
>
> On 11/4/05, Xavier Toth <tx...@gmail.com> wrote:
> >
> > I have a situation where I'm running a service and a client of the same
> > service in one vm. So I've deleted the wsdl2java generated type (the type of
> > the argument to a service method) because I have a jar with the actual type
> > already. The argument type contains a String and a byte[] and the byte[] is
> > the part that isn't getting to the service correctly. I'm not sure if it is
> > a serialization or deserialization problem. I've added the typemapping from
> > my server side wsdd to my client wsdd but that didn't fix things. Any ideas?
> >
>
>
Re: client serialization without wsdl2java generated type
Posted by Anne Thomas Manes <at...@gmail.com>.
If you have two Java applications running in the same VM, why are you using
SOAP to communicate with them?
Anne
On 11/4/05, Xavier Toth <tx...@gmail.com> wrote:
>
> I have a situation where I'm running a service and a client of the same
> service in one vm. So I've deleted the wsdl2java generated type (the type of
> the argument to a service method) because I have a jar with the actual type
> already. The argument type contains a String and a byte[] and the byte[] is
> the part that isn't getting to the service correctly. I'm not sure if it is
> a serialization or deserialization problem. I've added the typemapping from
> my server side wsdd to my client wsdd but that didn't fix things. Any ideas?
>