camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1057) XQuery creates an empty out message that makes it impossible to chain more processors behind it
Date Fri, 07 Nov 2008 07:08:05 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47160#action_47160
] 

Claus Ibsen commented on CAMEL-1057:
------------------------------------

Balazs could you re attach the patch with the ASF license granted. We can not accept patches
without this license.

The general rule with JIRA is *not* to attach files while creating the ticket. Only attach
files *afterwards* since then there is a checkbox where you can grant the ASF license.

> 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
>            Priority: Critical
>             Fix For: 1.5.1
>
>         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.


Mime
View raw message