You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Park033 <pa...@gmail.com> on 2010/01/21 12:42:32 UTC
CDATA problems
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.
Re: CDATA problems
Posted by Park033 <pa...@gmail.com>.
Thanks for your response Paul, I'll check this.
Paul Brown-5 wrote:
>
>
> 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 <pa...@gmail.com> 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.
>>
>
>
--
View this message in context: http://old.nabble.com/CDATA-problems-tp27256479p27272943.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: CDATA problems
Posted by Paul Brown <pa...@gmail.com>.
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 <pa...@gmail.com> 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.
>