That would probably explain it. The xml parser optimized and instead of
escaping everything (> instead of >), it just made a CDATA. If you
want the xml to be embedded in the document, try returning a Document or
Source object.
- Dan
Kees de Kooter wrote:
It is a string containing xml.
On 5/2/06, Dan Diephouse <[EMAIL PROTECTED]> wrote:
I'm going to guess that you're outputting something in the response
message that is forcing the xml parser to go to CDATA instead of just
straight up text. What is your response message?
- Dan
Kees de Kooter wrote:
> I created a simple test webservice using XFire & Spring.
>
> I publish a bean with the following method: public String
getMessage();
>
> In the soap result message it says
>
> <soap:Body>
> <getMessageResponse>
> <out><!CDATA[
> ....
> ]]>
> etc.
>
> Is it possible to get real xml as the message body, instead of CDATA?
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
