You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Jeong Ahn Lee <je...@yahoo.com> on 2002/06/24 08:50:17 UTC
Serialization problem!!
Hi all,
i am having a problem in serializing and
de-serializing the XML (Dom document)
what i am doing is i am creating a
org.w3c.dom.Document object ( SOAP Message)
i am digitally signing it using XML security suite
from apache( Digial Signature),
i am serializing it like below
// org.apache.xml.serialize.XMLSerializer;
XMLSerializer serializer = new XMLSerializer();
String docString = serializer.writeToString(doc);
and de-serializing it like below
DocumentBuilderFactory dbf =
DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse(new InputSource(new
StringReader(docString)));
but what happens is in these processes(serializiation
and de-serialization) the document
get modified and my signature verification fails.
what should i do to avoid this. what i am doing is
correct?
for me serializiation and de-serialization is very
important because, i need to send that
document over HTTP.
Thanks in advance
Jeong Ahn
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Serialization problem!!
Posted by Scott Nichol <sn...@scottnichol.com>.
Your issue sounds germaine to XML, not SOAP. Be certain to try post your
question to the relevant list.
Scott
----- Original Message -----
From: "Jeong Ahn Lee" <je...@yahoo.com>
To: <so...@xml.apache.org>; <so...@xml.apache.org>
Sent: Monday, June 24, 2002 2:50 AM
Subject: Serialization problem!!
> Hi all,
>
> i am having a problem in serializing and
> de-serializing the XML (Dom document)
>
> what i am doing is i am creating a
> org.w3c.dom.Document object ( SOAP Message)
> i am digitally signing it using XML security suite
> from apache( Digial Signature),
>
> i am serializing it like below
>
> // org.apache.xml.serialize.XMLSerializer;
>
> XMLSerializer serializer = new XMLSerializer();
> String docString = serializer.writeToString(doc);
>
>
> and de-serializing it like below
>
> DocumentBuilderFactory dbf =
> DocumentBuilderFactory.newInstance();
> DocumentBuilder db = dbf.newDocumentBuilder();
> Document doc = db.parse(new InputSource(new
> StringReader(docString)));
>
>
> but what happens is in these processes(serializiation
> and de-serialization) the document
> get modified and my signature verification fails.
>
> what should i do to avoid this. what i am doing is
> correct?
>
> for me serializiation and de-serialization is very
> important because, i need to send that
> document over HTTP.
>
> Thanks in advance
> Jeong Ahn
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Serialization problem!!
Posted by Scott Nichol <sn...@scottnichol.com>.
Your issue sounds germaine to XML, not SOAP. Be certain to try post your
question to the relevant list.
Scott
----- Original Message -----
From: "Jeong Ahn Lee" <je...@yahoo.com>
To: <so...@xml.apache.org>; <so...@xml.apache.org>
Sent: Monday, June 24, 2002 2:50 AM
Subject: Serialization problem!!
> Hi all,
>
> i am having a problem in serializing and
> de-serializing the XML (Dom document)
>
> what i am doing is i am creating a
> org.w3c.dom.Document object ( SOAP Message)
> i am digitally signing it using XML security suite
> from apache( Digial Signature),
>
> i am serializing it like below
>
> // org.apache.xml.serialize.XMLSerializer;
>
> XMLSerializer serializer = new XMLSerializer();
> String docString = serializer.writeToString(doc);
>
>
> and de-serializing it like below
>
> DocumentBuilderFactory dbf =
> DocumentBuilderFactory.newInstance();
> DocumentBuilder db = dbf.newDocumentBuilder();
> Document doc = db.parse(new InputSource(new
> StringReader(docString)));
>
>
> but what happens is in these processes(serializiation
> and de-serialization) the document
> get modified and my signature verification fails.
>
> what should i do to avoid this. what i am doing is
> correct?
>
> for me serializiation and de-serialization is very
> important because, i need to send that
> document over HTTP.
>
> Thanks in advance
> Jeong Ahn
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
How to Write XSP Code - equivalent to Java Soap Clients
Posted by deepak venugopal <de...@yahoo.com>.
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: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Java Equivalent Code for XSP
Posted by Scott Nichol <sn...@scottnichol.com>.
Have you tried posting this question to a cocoon mailing list? Perhaps the
author of the original soap.xsl or someone else familiar with cocoon can be
of more help than the folks on this list.
Scott Nichol
----- Original Message -----
From: "deepak venugopal" <de...@yahoo.com>
To: <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
Sent: Monday, June 24, 2002 11:27 PM
Subject: Java Equivalent Code for XSP
> 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" <de...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Cc: <so...@xml.apache.org>
> > 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:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Java Equivalent Code for XSP
Posted by Scott Nichol <sn...@scottnichol.com>.
Have you tried posting this question to a cocoon mailing list? Perhaps the
author of the original soap.xsl or someone else familiar with cocoon can be
of more help than the folks on this list.
Scott Nichol
----- Original Message -----
From: "deepak venugopal" <de...@yahoo.com>
To: <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
Sent: Monday, June 24, 2002 11:27 PM
Subject: Java Equivalent Code for XSP
> 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" <de...@yahoo.com>
> > To: <so...@xml.apache.org>
> > Cc: <so...@xml.apache.org>
> > 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:
> > <ma...@xml.apache.org>
> > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Java Equivalent Code for XSP
Posted by deepak venugopal <de...@yahoo.com>.
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" <de...@yahoo.com>
> To: <so...@xml.apache.org>
> Cc: <so...@xml.apache.org>
> 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:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Java Equivalent Code for XSP
Posted by deepak venugopal <de...@yahoo.com>.
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" <de...@yahoo.com>
> To: <so...@xml.apache.org>
> Cc: <so...@xml.apache.org>
> 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:
> <ma...@xml.apache.org>
> > For additional commands, e-mail:
> <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> For additional commands, e-mail:
> <ma...@xml.apache.org>
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
Re: Serialization problem!!
Posted by Scott Nichol <sn...@scottnichol.com>.
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" <de...@yahoo.com>
To: <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
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: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Serialization problem!!
Posted by Scott Nichol <sn...@scottnichol.com>.
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" <de...@yahoo.com>
To: <so...@xml.apache.org>
Cc: <so...@xml.apache.org>
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: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Serialization problem!!
Posted by deepak venugopal <de...@yahoo.com>.
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
How to Write XSP Code - equivalent to Java Soap Clients
Posted by deepak venugopal <de...@yahoo.com>.
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
Re: Serialization problem!!
Posted by deepak venugopal <de...@yahoo.com>.
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: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>