[
https://issues.apache.org/activemq/browse/CAMEL-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59042#action_59042
]
Mitko Kolev commented on CAMEL-2549:
------------------------------------
Hi Thomas,
Thanks for the feedback!
I will check your use case today.
Some initial comments:
* You can easily access the {{stderr}} from the message headers. If there is no
{{stderr}}, the header value must be {{null}}.
* I assume you read the stream twice once in the log ( i suppose you do it once
again after the log). If there is a second read it will generally need a reset.
This is a common problem when you read from streams. Did you try using the
Camel stream caching for that route, I think it is designed exactly for such
cases.
{code}
I would have expected that the Converter would send the ExecResult stdErr() if
it is not null.
{code}
This is rather a design issue, that can be easily implemented, as you just
noticed. However, the solution you proposed will not work if the stream is not
resetable (this could be the case if someone is using a custom executor).
I will think over your suggestion and write back here later today.
Regards,
Mitko
> 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.
