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

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-1057.
--------------------------------

    Fix Version/s: 2.0.0
       Resolution: Fixed

Applied patch with thanks to Balazs

> XQuery creates an empty out message that makes it impossible to chain more processors behind it
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1057
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1057
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-saxon
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Balázs Zsoldos
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 1.5.1, 2.0.0
>
>         Attachments: XQueryBuilder.java.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.