You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (JIRA)" <ji...@apache.org> on 2017/03/06 13:54:32 UTC

[jira] [Created] (CAMEL-10950) Enable camel-docker configuration to accept a custom DockerCmdExecFactory

James Netherton created CAMEL-10950:
---------------------------------------

             Summary: Enable camel-docker configuration to accept a custom DockerCmdExecFactory
                 Key: CAMEL-10950
                 URL: https://issues.apache.org/jira/browse/CAMEL-10950
             Project: Camel
          Issue Type: New Feature
          Components: camel-docker
            Reporter: James Netherton
            Priority: Minor


One of the drawbacks with the docker-java library used in the camel-docker component is that it depends on Jersey for the JAX-RS client.

This can be problematic if you already have another JAX-RS implementation on the classpath.

Therefore, it'd be nice if you could specify the {{DockerCmdExecFactory}} that you want to work with. By default it'd be {{JerseyDockerCmdExecFactory}}, but you could choose to use the NettyDockerCmdExecFactory if you wanted to avoid Jersey. 

Similarly, users could implement their own DockerCmdExecFactory and have camel-docker load this when it comes to build the Docker client.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)