[
https://issues.apache.org/jira/browse/CAMEL-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180405#comment-13180405
]
Claus Ibsen commented on CAMEL-4713:
------------------------------------
Good work Scott.
In the endpoint, I would suggest not to both log error and throw exception.
Just throwing exception is fine. And use CamelExechangeException instead of
just Exception.
And add some debug/trace logging in the sendExecCommand so ppl can turn on
logging to see what the component is doing.
Does the await() method block forever? What would happen if there is no
physical connection? I assume it should be possible to set some timeout value.
In the producer, you may be aware that getOut will create a new empty message.
Which means that any headers is not preserved. So what we usually do is to copy
those headers. See for example TransformProcessor from camel-core.
> Create a camel component for SSH
> --------------------------------
>
> Key: CAMEL-4713
> URL: https://issues.apache.org/jira/browse/CAMEL-4713
> Project: Camel
> Issue Type: New Feature
> Reporter: Ioannis Canellos
> Fix For: 2.10
>
>
> Lately, I've seen a lot of questions in the mailing list for people that
> would want to use camel to execute SSH commands to remote hosts.
> I think it would be nice if we could provide such component to the users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
