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:[EMAIL PROTECTED]] Sent: Thursday, 21 March, 2002 5:41 PM To: [EMAIL PROTECTED] 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 '&'. If literal XML is used, the XML being serialized seems to be invalid. Scott Nichol ----- Original Message ----- From: "Henk Schipper" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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 '&' 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
