If I haven't mentioned before, a osgi service could also carry
properties. This is used as example in the OSGI JPA Spec. where it is
written:
> The service must be registered with the following service property:
> javax.persistence.provider – The JPA Provider implementation class
> name, a docu
I had a similar problem before:
In an osgi project we needed the ability to extend a main system with
functionality provided in addon bundles
We developed a main system which could be extended and complemented with
extenders of several kinds.
The main system provided (exported) a tree of marker
only one method getClassLoader()) - and
hibernate could track/listen to services which implement this marker
interface.
>
>
> On Tue 28 Aug 2012 02:13:15 PM CDT, mail...@bibbernet.org wrote:
>> On 08/28/2012 02:39 PM, Steve Ebersole wrote:
>>> The problem there is timing.
On 08/28/2012 02:39 PM, Steve Ebersole wrote:
> The problem there is timing. Hibernate already has to be started in order
> for "this" to work. But what "this" is doing is providing things Hibernate
> needs to start. Its chicken-egg.
>
> Interestingly this is very similar to the proposal Scott M
OSGI has two classes/interfaces for dealing with Service Tracking -
ServiceTracker and ServiceTrackerCustomizer, which could be used to
create a OSGI-auto-discovery (and auto-cleanup)-Helper for hibernate:
A simple skeleton could look like:
package org.bibbernet.osgi;
import org.osgi.framework
Hello,
because I need clean OSGI bundles for Hibernate and especially Envers, I
am working on some patches for the 4.1 branch of hibernate-orm to enable
generation of OSGI compatible jar files.
During the work I have found the following problems, and need some help
and/or feedback. The probl
