I think the problem comes because of the characters like "<" and ">" in your XML which is returned as a string inside the SOAP envelope XML. I am not very sure, but you can still see if the following works:
Replace all the "<",">" and "\" (and any other characters that might pose problems) in the string (XML) you return by "<", ">" and """ respectively. At the client, do the reverse process to get your XML.
- Sai
On 6/20/06, akkachotu <[EMAIL PROTECTED]> wrote:
I hava rpc encoded style web service that returns a string as
response. In the string I'll storing a xml file which has CDATA
sections and some inline DTD. My problem is sometimes I am getting an
error from axis serialization classes saying that there is an invalid
character in xml.
So is it better to convert the xml data into a BASE64 string (may be
using AXIS API Or Jakarta Commons API) and return that string as
response ? or is there any other way of doing returning xml files as
strings ?
Please suggest.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
