[CAMEL-1057] XQuery creates an empty out message that makes it impossible to chain more processors behind it

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.4.0, 1.5.0
• Fix Version/s: 1.6.0, 2.0-M1
• Component/s: camel-saxon
• Patch Info: Patch Available
• Assignee: Claus Ibsen
• Reporter: Balazs Zsoldos
• Created: 07/Nov/08 00:56
• Updated: 31/Jul/09 06:33
• Resolved: 07/Nov/08 13:23

Description

When using XQuery the getOut() function is called on the message so if it is not used at a place where the out is filled an empty out message will be created. With this xquery cannot be used for example in setBody, setHeader... and anywhere where the out is not filled.
An example where this causes real trouble:

<choice>
<when>
<xquery>...</xquery>
<to uri="direct:follow" />
</when>
</choice>

...
<from uri="direct:follow">
<to ...>
<to ...>

In the patch the out property in the xquery context is filled only if it is not null. With it all of my pipelines seem to work well for me.