CDATA is not visible to the engine; it is only a hint for the parser
to know whether to process markup or just pass characters through, so
it shouldn't be used by an application — the app should just consume
characters.
If you really need CDATA, then you can use an XSLT processor (outside
on the engine) to get it. (Look up cdata-section-elements or some
such.)
--
Sent from my iPhone; it is responsible for any typos or grammatical
errors.
On Jan 21, 2010, at 3:42 AM, Park033 <[email protected]> wrote:
Hi,
Although all my messages have CDATA (msg IN and OUT), they're all
removed as
soon as they're arriving in my bpel process.
how can I do to at least keep CDATA from messages generated and sent
by my
process ?
If someone have any idea of this, I'd be really grateful.
Regards,
--
View this message in context:
http://old.nabble.com/CDATA-problems-tp27256479p27256479.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
