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<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 "<" and
">" to ">". This should be done in the SOAP library,
I think...