[
https://issues.apache.org/jira/browse/CAMEL-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897951#comment-15897951
]
ASF GitHub Bot commented on CAMEL-10950:
----------------------------------------
GitHub user jamesnetherton opened a pull request:
https://github.com/apache/camel/pull/1509
CAMEL-10950: Enable configuration of a custom DockerCmdExecFactory
https://issues.apache.org/jira/browse/CAMEL-10950
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jamesnetherton/camel CAMEL-10950
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1509.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1509
----
commit 16f60a5caaf05fd928060300d1ce25c85683df4b
Author: James Netherton <[email protected]>
Date: 2017-03-06T12:14:43Z
CAMEL-10950: Enable configuration of a custom DockerCmdExecFactory
----
> 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
> Assignee: 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)
