[
https://issues.apache.org/activemq/browse/CAMEL-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59049#action_59049
]
Thomas Demande commented on CAMEL-2549:
---------------------------------------
Hi Mitko,
Thanks for your fast reply!
I took a look at what you said and it actually helped a lot:
About the needed reset, I was indeed 'reading' the stream twice, as I used
{{trace="true"}} for my context...
Not using it does make the result appear in the log.
However, using stream caching does not help at all, so in a route using the
wireTap pattern such as:
{code:xml}
<route streamCache="true">
<from uri="direct:testExec" />
<to uri="exec:dir"/>
<wireTap uri="seda:wireTap"/>
<to uri="seda:treatResult" />
</route>
{code}
the {{treatResult}} route would be unable to read the exec result without
resetting it (with a bean?).
About the stdErr design, I think that the current SVN state makes using the
exec component problematic in a "pure" Spring XML notation (without being
'forced' to use beans).
I think a basic usage of this component would be to launch the exec, then route
the message using a CBR, based on the return code. Each route should then IMHO
be able to get the exec result without being aware of the stream where it is
located (err or out).
As you said, always restting streams in the converter would cause issues for
streams that would throw an exception when calling reset(), but I really think
that being able to use this component _transparently_ in the basic usage I
described is a must have ;)
> Camel Exec component
> --------------------
>
> Key: CAMEL-2549
> URL: https://issues.apache.org/activemq/browse/CAMEL-2549
> Project: Apache Camel
> Issue Type: New Feature
> Affects Versions: 2.3.0
> Environment: Tested on Windows XP and Linux
> Reporter: Mitko Kolev
> Assignee: Martin Krasser
> Fix For: 2.3.0
>
> Attachments: camel-exec-3.diff, camel-exec-component-feedback.zip,
> camel-exec-patch.diff, camel-exec-patch2.diff, exec-wiki.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
