karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4133) Run EclipseLink and Hibernate together within Karaf
Date Mon, 07 Dec 2015 09:06:11 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044608#comment-15044608

Guillaume Nodet commented on KARAF-4133:

Fwiw, features can deal with scoping the same way as subsystems.  So one could define two
different regions, add hibernate in the first one and eclipse link in the second one so that
they would not conflict.

> feature:install --region root/hibernate hibernate
> feature:install --region root/eclipselink eclipselink 

> Run EclipseLink and Hibernate together within Karaf
> ---------------------------------------------------
>                 Key: KARAF-4133
>                 URL: https://issues.apache.org/jira/browse/KARAF-4133
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>    Affects Versions: 3.0.5
>            Reporter: Andy Schmidt
>             Fix For: 3.0.6, 4.0.4
>         Attachments: EclipseLink_Hibernate_with_Karaf.pdf
> In my company we are using Karaf 3.0.5 as application container to different applications.
We have the situation to run Hibernate and EclipseLink as JPA implementation together within
a single Karaf, because different applications use different JPA implementations. Which kind
of implementation is used is defined by the persistence unit of each application.
> I wrote an article which describes how to get the most important Java Persistence API
(JPA) implementations, EclipseLink and Hibernate, running together within a single Apache
Karaf. The article describes why this is not possible with the current Karaf enterprise feature
definitions and what has to be done to make it work. I will add the article to this issue
description. Please read my article and I hope you can change the enterprise feature definition
descripte in the article to get this possible.

This message was sent by Atlassian JIRA

View raw message