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

Claus Ibsen commented on CAMEL-6120:
------------------------------------

Thanks Scott. I have applied the patch to trunk.

I think with the BC dependency we need to add that to the features.xml file, so 
camel-ssh can be installed in Karaf out of the box.

Also can you update the documentation for the camel-ssh component.

And it would be excellent if you added a page about these 2 examples at
http://camel.apache.org/examples

And explained the example and highlighted interesting parts of the code of the 
example, as we do with the other examples we have. Also maybe add some notes 
about you should have Apache Karaf running when staring the example so it can 
connect to it (eg if you run using mvn camel:run).
                
> camel-ssh - Use ResourceHelper to load keystore so its easy loadable from 
> classpath/file etc
> --------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6120
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6120
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ssh
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: Future
>
>         Attachments: CAMEL-6120.patch
>
>
> See
> https://github.com/scranton/example-security-camel-ssh/blob/master/src/main/resources/META-INF/spring/camel-context.xml
> Having to create a custom key factory to use a classloader is too complicated.
> We should use the code from util package in camel-core ResourceHelper which 
> we use in other components to load resource files from classpath / file etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to