The attribute messageExchange was introduced in BPEL 2 to allow for distinguishing between overlapped message exhanges.
The v1.1 schema allows for extensible attributes of other namespaces in the receive activity, which does not include local attributes. Therefore you can only use messageExchange if your document conforms to the v2 schema. BPEL 2 further states that "if the messageExchange attribute is not specified on a receive then its value is taken to be empty". This is the value receive activities from v1 documents use internally. Maybe the empty string is being saved as a SQL NULL in Oracle? I need to ask the JBoss QA team as I don't have Oracle in my dev machine (neither do I want to!). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913263#3913263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913263 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user