Integration

Hi,

I'm building a process that is initiated with a lookup value containing open and close square brackets. Not my idea. However, when I pass the value to the bpel process, the close bracket is interpreted by the BPEL xml parser as an end tag, so my value is truncated. To make matters worse, if I try to embed the value in a CDATA tag, the parser claims it is invalid XML.

This is what the data being passed in looks like without the CDATA:

<StoredProcTestProcessRequest xmlns="http://xmlns.oracle.com/StoredProcTest">
<readingType>test[33]</readingType>
</StoredProcTestProcessRequest>

This is the resulting value that I see further on in the process:

test[33

This is what the data being passed in looks like with the CDATA:

<StoredProcTestProcessRequest xmlns="http://xmlns.oracle.com/StoredProcTest">
<readingType>
<![CDATA[
test[33]
]]>
</readingType>
</StoredProcTestProcessRequest>

Here's the error I see in that case:

<2005-09-08 15:41:17,937> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle
dispatch message ... exception ORABPEL-05002

Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeIns
tanceMessage"; the exception is: The XML data is invalid.
The XML data is invalid; the reason is "null Nested exception: null".
Please verify xml data.

Does anyone have a workaround for this?

Thanks,
Chris