ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henk Schipper" <henk.schip...@software684.com>
Subject RE: Parsing &-sign
Date Fri, 22 Mar 2002 09:03:13 GMT
Hi Scott,

Thx. You are right. I forgot the serializer. I had to write one because the
standard one was not applicable for this project.
You pointed me in the right direction. Thanks

Henk.

-----Original Message-----
From: Scott Nichol [mailto:scottnicholnews@yahoo.com]
Sent: Thursday, 21 March, 2002 5:41 PM
To: soap-dev@xml.apache.org
Subject: Re: Parsing &-sign


Henk,

How is the message encoded (SOAP, XML literal or XMI)?  When using SOAP
serialization, the default serializer for the String type uses
org.apache.soap.Utils#cleanString, which would convert a bare '&' to
'&amp;'.
If literal XML is used, the XML being serialized seems to be invalid.

Scott Nichol

----- Original Message -----
From: "Henk Schipper" <henk.schipper@software684.com>
To: <soap-dev@xml.apache.org>
Sent: Thursday, March 21, 2002 10:08 AM
Subject: Parsing &-sign


> Hi all,
>
> I have been searching for this but, no results:
>
> Using:
> apache-tomcat 3.2.1 (very stable)
> xerces 1.3.0
> soap 2.2
>
> Error:
> In a xml-response, there is an '&' in a field. This message goes wrong,
> although no response is coming out of the client.
> When the character '&' is replaced by '&amp;' it goes allright. Anyone got
> any idea? where in the parser does this one go wrong. Is there an update?
>
> I got no error description at the moment. This happens not on our system
> internally, only at a customers-site.
>
> Thanks in advance for your comments.
>
> Henk Schipper.
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




Mime
View raw message