You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Timothy Ward (JIRA)" <ji...@apache.org> on 2010/03/01 19:58:05 UTC

[jira] Resolved: (ARIES-202) Separate the blueprint integration from the container context management

     [ https://issues.apache.org/jira/browse/ARIES-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Ward resolved ARIES-202.
--------------------------------

    Resolution: Fixed

The JPA runtime now exists as four bundles:

An API bundle

A bundle for basic App Managed JPA via the OSGi Service Registry

A bundle for Container managed persistence contexts

A bundle for blueprint injection of JPA resources

> Separate the blueprint integration from the container context management
> ------------------------------------------------------------------------
>
>                 Key: ARIES-202
>                 URL: https://issues.apache.org/jira/browse/ARIES-202
>             Project: Aries
>          Issue Type: Improvement
>          Components: JPA
>    Affects Versions: 0.1
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>             Fix For: 0.1
>
>
> Currently the org.apache.aries.jpa.container.context bundle does blueprint integration as well as managed context support. This should be split apart to make it easier to integrate other injection methods (for example the blueprint RI).

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