aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (JIRA)" <>
Subject [jira] [Assigned] (ARIES-736) Aries does not take into account the concept of complete/incomplete Persistence Units
Date Tue, 30 Aug 2011 08:10:38 GMT


Timothy Ward reassigned ARIES-736:

    Assignee: Timothy Ward

> Aries does not take into account the concept of complete/incomplete Persistence Units
> -------------------------------------------------------------------------------------
>                 Key: ARIES-736
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>    Affects Versions: 0.3
>            Reporter: Christoph Läubrich
>            Assignee: Timothy Ward
> The OSGi spec states (r4.2 127.3.1):
> "Entity Manager Factory service - Provides an EntityManagerFactory object that depends
on a complete
> Persistence Unit. That is, it is associated with a registered Data Source Factory service."
> The current behaiviour is, that aries registers a Entity Manager Factory service regardles
of the precence of a matching Data Source Factory service (Also see 127.5.3 Data Source Factory
Service Matching).
> If no such matching is performed, it alternateively must register a Entity Manager Factory
Builder service (not currently supported by Aries see ARIES-735 for reference).
> What infact is unclear to me is:
> 127.5.3 states that: "Once the Data Source Factory is obtained, the JPA Provider must
obtain a DataSource object. This
> Data Source object must then be used for all relational database access."
> It does not state how this DataSource could be handed over to the PersistenceProvider
for later usage.
> It might be suitable to insert a level of indirection here:
> - Aries just reads the persitence units and registers an Entity Manager Factory Builder
> - PersistencProvider specific bundles match these with the required data source and register
the Entity Manager Factory service

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message