aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <>
Subject [jira] Commented: (ARIES-81) Implement support for PersistenceUnit service
Date Thu, 10 Dec 2009 12:10:19 GMT


Timothy Ward commented on ARIES-81:

There is no PersistenceUnitInfoService class defined by the draft specification of the OSGi
Persistence Unit service or the Java Persisence API specifications. We should not implement
an OSGi interface that does not exist in the public domain. 

The most recent public draft of the OSGi Persistence Unit Service is here:

I believe ARIES-79 and 80 are better places to start with the Aries JPA support.

> Implement support for PersistenceUnit service
> ---------------------------------------------
>                 Key: ARIES-81
>                 URL:
>             Project: Aries
>          Issue Type: New Feature
>          Components: JPA
>            Reporter: Alan Keane
> The Persistence Unit service acts as the client doorway to JPA. It is registered under
> org.osgi.jpa.PersistenceUnit service interface name. Clients that want to access and
> operate on entities in a particular named persistence unit look up the service and use
it to obtain a
> JPA entity manager factory, from which an entity manager and other JPA artifacts can
> subsequently obtained.
> The service is implemented as a ServiceFactory so that when a client looks up the service
> provider can identify the dependencies of the calling client. The provider must then
create an entity
> manager factory for the persistence unit version corresponding to the calling client's

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message