RE: Problem with < and > as parameter value

[Eduardo Y�nez]

Why a different encoding??, isn�t this a String serializer bug??, it should
escape all XML-reserved (<, >, &, �, ") symbols (i think...)

Regards,
Eduardo Y�nez.

-----Original Message-----
From: Rob Englander [mailto:[EMAIL PROTECTED]]
Sent: Jueves, 23 de Agosto de 2001 08:57 a.m.
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.

-----Original Message-----
From: Micael Ericsson (QIN) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 4:56 AM
To: '[EMAIL PROTECTED]'
Subject: Problem with < and > as parameter value


Hello

If I call a service and supply a parameter with <aa> as parameter value this
is interpret in XML correctly as &lt;aa&gt;, but reaching Apache Soap (ver
2.2 on tomcat 3.2.3) I get the following error message:
Exception: java.lang.Exception:SOAPException= SOAP-ENV:Client, Parsing
error, response was: The element type "aa" must be terminated by the
matching end-tag "
".

Is this a bug in apache soap toolkit?
Or have I missed some setting?

Thanks in advance,
Micael Ericsson