Re: Problem with < and > as parameter value

[David Wall]

Save yourself some headaches with mapping ']]>' to ']]>' and just map '>'
to '>' and you've got a good translation list for XML strings.

David


----- Original Message -----
From: "Ed Yu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 8:07 AM
Subject: RE: Problem with < and > as parameter value


> Here is what I've recently worked with to translate special characters
into
> proper XML:
>
>
>  charater/sequence            entity reference(replacement)
>             &                                 &amp;
>           ]]>                                  ]]&gt;
>            <                                   &lt;
>
> Unfortunately, I don't recall where the source of it is from. Good Luck!
>
> -----Original Message-----
> From: Micael Ericsson (QIN) [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 23, 2001 10:53 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Problem with < and > as parameter value
>
>
> When using TcpTunnelGUI to monitor XML messages transfer I can see that
the
> sent string "good<day" (as parameter value to a service method) in the XML
> message has the text "good&lt;day".
>
> After that Xerces/JAXP converts/serializes this to a String, but something
> goes wrong and a error message is returned to SOAP client.
>
> I have tested this on Xerces 1.2.3 and 1.4.3, and JAXP 1.1. All versions
> gives error but different error messages.
>
> Bug in XML perser/String serializer or encoding setting?
> Anyone know where to find specifivcation for which characters are possible
> to user as request parameter values.
>
> /Micael E.
>
> -----Original Message-----
> From: Paco Avila [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 23, 2001 4:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with < and > as parameter value
>
>
> > That's because you can't have special characters
> > like < and > in your strings.  Try encoding them
> > using base64 encoding.
>
> The "<" character shold be converted to "&lt;" and
> ">" to "&gt;". This should be done in the SOAP library,
> I think...