Actually, if your error really is "no serializer found for org.w3c.node",
then this means the server cannot find a serializer, which very likely means
your Java clients use literal XML encoding.
Scott Nichol
----- Original Message -----
From: "Scott Nichol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 24, 2002 3:57 PM
Subject: Re: Serialization problem!!
> Please check your Java clients that handle a return Element. I suspect
they
> either use literal XML encoding (not SOAP encoding) or they add a
> deserializer for Element to the mapping registry. Your XSP code must, of
> course, do the same in order to work.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "deepak venugopal" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, June 24, 2002 8:02 AM
> Subject: Re: Serialization problem!!
>
>
> > Hello friends,
> > My company has started developing soap clients based
> > on XSP and submitting the request to Apache Soap
> > Server which has services running in pure Java.
> > For my Java Soap Clients, the soap service used to
> > return a Node Element ( XML Document). The Java Client
> > worked perfectly using the usual following code:
> >
> > if( !resp.generatedFault() )
> > {
> > Parameter ret = resp.getReturnValue();
> > bookEl = (Element)ret.getValue();
> >
> > System.out.println(DOM2Writer.nodeToString(bookEl));
> >
> > }
> >
> > But now since i have started using XSP where the
> > client looks like :
> > <soap:call url="http://soap server .....">
> > <ns1:*method name *
> > xmlns:ns1="urn:*service name *">
> > <soap:enc/>
> > <symbol xsi:type="xsd:string"
> > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
> > xmlns:xsd="http://www.w3.org/1999/XMLSchema";><xsp-request:get-parameter
> > name="symbol"/></symbol>
> > </ns1:*method name*>
> > </soap:call>
> >
> > ,while working with string return values, the existing
> > sample code works perfectly, but when xml objects r
> > being rcvd i get the error no serializer found for
> > org.w3c.node***.
> > (-- i can solve this error for Java Clients--)
> >
> >
> > Since there are no existing cases in the mail archives
> > for writing the XSP equivalent of exisiting Java
> > Clients or any literature on the Net, we are facing
> > great problems.
> > If any of you guys have sorted out these kinda XSP
> > cases, pls do reply as it wld b of gr8 help.
> > rgds
> > DEEPAK.
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> >
> > --
> > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >
> >
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
