camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-7377) mark openjpa as dependency in Camel JPA feature
Date Fri, 25 Apr 2014 05:59:14 GMT


Claus Ibsen commented on CAMEL-7377:

Hmm openjpa should really not be there, as people should install their JPA implementation
of choice. So if they want to use something else such as EclipseLink or Hibernate then OpenJPA
should not be installed out of the box.

> mark openjpa as dependency in Camel JPA feature 
> ------------------------------------------------
>                 Key: CAMEL-7377
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jpa
>    Affects Versions: 2.12.3, 2.13.0
>            Reporter: Ioan Eugen Stan
> I believe Camel-JPA feature should mark openjpa bundle as a dependency becasue it conflicts
with open-jpa 2.3.0. 
> Currently camel-jpa feature.xml defines: 
> ```
> <bundle>mvn:org.apache.openjpa/openjpa/2.2.2</bundle>
> ```
> and should be <bundle dependency="true">mvn:org.apache.openjpa/openjpa/2.2.2</bundle>

> This problem apears when you have openjpa 2.3.0 installed and with to install camel-jpa
2.12.3 feature.  
> Not marking the bundle as a dependency results in camel-jpa pulling the OpenJPA 2.2.2
bundle even if karaf has OpenJpa 2.3.0. Since both bundles try to register a PersistenceProvider
in OSgi, the second one fails and the bundle fails to start - so camel-jpa feature is not

This message was sent by Atlassian JIRA

View raw message