You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2015/03/24 07:48:52 UTC

[jira] [Resolved] (CAMEL-8536) Using JCR API 2.0 jar which is already OSGi bundle

     [ https://issues.apache.org/jira/browse/CAMEL-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-8536.
---------------------------------
    Resolution: Fixed

Applied the patch camel master, camel-2.15.x and camel-2.14.x branches.

> Using JCR API 2.0 jar which is already OSGi bundle
> --------------------------------------------------
>
>                 Key: CAMEL-8536
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8536
>             Project: Camel
>          Issue Type: Improvement
>          Components: osgi
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.14.3, 2.15.1, 2.16.0
>
>
> Current ServiceMix JCR API 2.0 bundle 2.4 is not generated right. AS the JCR API bundle is already OSGi bundle, we should use it directly.
> BTW, I checked the code of camel-jcr, the user need to setup the Repository directly to the JCR endpoint, so we don't need to leverage the service locator lookup feature that servicemix spec provides.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)