hi friends, my previous message was as listed below. The thing is in my Java soap clients i have modified the CALL Objects encoding style with : call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML); and have successfully obtained the return ELEMENT from my Java Soap Service.( I had mentioned this earlier).
While working with XSP, ( samples - xscript / soap-getqoute1.xsp,soap-getquote2.xsp) i noticed it had a tag mentioning <soap:enc> which probably was talkin abt the encoding style. Since the xsp's where handled by the style sheets - soap.xsl (--path org/apache/cocoon/components/language/markup/xsp/java/soap.xsl--) i had put a new tag in the style sheet as <soap:enc1> referecing it to : "http://xml.apache.org/xml-soap/literalxml/"; in the style sheet. However inspite of using <soap:enc1> it was still using the pervious encoding <soap:enc> which was referrring to " http://schemas.xmlsoap.org/soap/encoding/";.. Anyway the bottom line is , are there any cases where XSP's have been used flexibly for sending XML documents, receiving XML documents, for Messaging etc as shown in the Java Soap Client Samples bundles with the Apache SOAP software. If so pls do revert. I wld b extremely gr8ful. regards DEEPAK. > > ----- 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]> > __________________________________________________ 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]>
