You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2017/05/10 12:50:05 UTC

[jira] [Commented] (CAMEL-11256) Make camel-docker work on OSGi

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

Andrea Cosentino commented on CAMEL-11256:
------------------------------------------

+1 for me. It makes sense and we can add a Karaf feature

> Make camel-docker work on OSGi
> ------------------------------
>
>                 Key: CAMEL-11256
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11256
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-docker
>            Reporter: James Netherton
>            Priority: Minor
>
> Seems this was attempted before in CAMEL-10304 but was ultimately dropped because of issues getting Jersey to work (see [here|https://github.com/apache/camel/commit/7db9c8e5e8f5822e8e36c0dc947b7e8dec242b7b]). There are similar issues in environments where other JAX-RS provides are already present (like JavaEE containers).
> Now that the docker-java client supports a {{NettyDockerCmdExecFactory}}, I wonder if we make this the default on Camel and make the Jersey dependencies optional (or exclude them)?
> If folks want the Jersey impl, they're free to add the relevant dependencies to their project and configure the {{JerseyDockerCmdExecFactory}} via the {{cmdExecFactory}} endpoint config param.
> Thoughts?



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