Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <231598650.1243367325668.JavaMail.jira@brutus>
Date: Tue, 26 May 2009 12:48:45 -0700 (PDT)
From: "Donald Woods (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Assigned: (OPENJPA-767) Better OSGi Integration
In-Reply-To: <2022293537.1226426864215.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Donald Woods reassigned OPENJPA-767:
------------------------------------

    Assignee: Donald Woods  (was: Kevin Sutter)

> Better OSGi Integration
> -----------------------
>
>                 Key: OPENJPA-767
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-767
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: third-party
>    Affects Versions: 1.3.0
>            Reporter: Kevin Sutter
>            Assignee: Donald Woods
>             Fix For: 1.3.0, 2.0.0
>
>
> The ability to use OpenJPA in an OSGi "container" environment is a desired feature.  Basically, OSGi could provide the "container" aspect of the Java EE environment.  This would be beyond the basic JSE application-managed persistence context support.  And, it's not quite the same as the defined Java EE container-managed persistence context support.  It's similar though.
> We can use this feature to document items that come along from this exercise.  To start with, I will probably create a separate branch/sandbox for experimentation.  Once we get a better handle on the extent of the changes, then we will need to merge any necessary changes into the appropriate supported branch or trunk.

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