Hey Edwin,
I'm being bugged by almost the same problem man. I have read all the related
archive messages but couldn't find what's going wrong with my code. Actually
my data transfer webservice was working perfect for last many months. But
broke down 2 days ago when an update was made on the destina
I forgot to say that the bean mapping goes in your deployment descriptor in
the deploy section outside of the service section. Meaning
...
On Wednesday 30 July 2003 02:51 pm, List Man wrote:
> If you are getting this error on the server side you prob
If you are getting this error on the server side you probably need a bean
mapping like so.
On Wednesday 30 July 2003 04:42 am, Kareem Ghazal wrote:
> Hello,0
>
> I'm using the IBM's WSDK which uses axis. I figured out how to set the
> serializer/deserializer on the client by getting hold of the
lass, however I still get a "Deserializer not found" exception.
> So how do I set the serializer and deserializer on the server from my
> client?
>
> Thanks
> Kareem
>
> Original Message Follows
> From: Davanum Srinivas <[EMAIL PROTECTED]>
> Reply-To: [
MAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Deserializer not found
Date: Tue, 22 Jul 2003 03:36:51 -0700 (PDT)
yes, you need it on both sides. you need to specify it in when deploying the
service using
beanmapping tags.
-- dims
--- "Kareem S. Ghazal" <[EMAIL PROTECTED]> wrote:
&g
yes, you need it on both sides. you need to specify it in when deploying the service
using
beanmapping tags.
-- dims
--- "Kareem S. Ghazal" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm using IBM's WSDK which uses axis. I figured out how to set the
> serializer/deserializer by getting hold of th
