camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gonzalo Vasquez <gvasq...@altiuz.cl>
Subject Exec endpoint not working correctly with recipientList
Date Thu, 14 Aug 2014 16:18:50 GMT
Hi there!

Experimenting with the exec endpoint I found out that it works perfectly (setting CamelExecExitValue
header) when invoked with hardcoded args, such as:

<camel:to uri="exec:///opt/ibm/ondemand/V9.0/bin/arsload?args=-f -g FONDO -h 192.168.10.77
-u admin -p password /tmp/ID-MacBook-Pro-de-Gonzalo-Vasquez-local-64241-1408030173940-0-1"
/>



But fails silently on setting headers (CamelExecExitValue not set, and blank body )when invoked
as a receipientList endpoint, with variable parameters such as:

                                <camel:recipientList>
                                        <camel:simple>
                                exec://{{cmod.arsLoad}}?args=-f -g ${in.header.appGroup} -h
{{cmod.host}} -u {{cmod.username}} -p {{cmod.password}} {{tmp.path}}/${id}</camel:simple>
                                </camel:recipientList>


I actually need to use the second approach as the arguments to my command are determined in
runtime.

Am I doing something wrong or the recipientList actually removed the expected headers?


PS: This is derived from my previous post at http://camel.465427.n5.nabble.com/Retrieving-EXEC-EXIT-VALUE-from-exec-endpoint-td5755188.html

Regards,

Gonzalo Vasquez
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message