[CAMEL-10950] Enable camel-docker configuration to accept a custom DockerCmdExecFactory

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.19.0
• Component/s: camel-docker
• Estimated Complexity: Unknown
• Assignee: James Netherton
• Reporter: James Netherton
• Created: 06/Mar/17 13:53
• Updated: 07/Mar/17 12:50
• Resolved: 07/Mar/17 12:50

Description

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.

Issue Links

• links to: GitHub Pull Request #1509