[
https://issues.apache.org/jira/browse/OPENJPA-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737226#comment-16737226
]
Matt Pavlovich commented on OPENJPA-2766:
-----------------------------------------
[~romain.manni-bucau] The ReloadableEntityManagerFactory looks pretty close. I
agree, #2 does not need to be a part of OpenJPA. My intention was to suggest
that the design in #1 could be done in a way to support #2.
Regarding Features-2 in the ticket description is that the
ReloadableEntityManagerFactory appears to rely on Classloader scanning. If the
API also supported addManagedClasses(Class<?> managedClass), then OSGi bundles
could add and remove their manged/enhanced classes as part of the bundle
lifecycle and eliminate the Classloader headaches.
https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/ReloadableEntityManagerFactory.java#L468
> Modularity support
> ------------------
>
> Key: OPENJPA-2766
> URL: https://issues.apache.org/jira/browse/OPENJPA-2766
> Project: OpenJPA
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Priority: Major
>
> Support modular organization of entities so that all entities do not need to
> be contained in the same jar, or referenced in a single persistence.xml
> <class> listing.
> Use cases:
> 1. Jar A contains entityA, Jar B contains entityB. (EntityB may or may not
> extend from entityA.)
> 2. Jar X contains persistence.xml defining the PU
> 3. Jar C contains entityC and a list of classes that extend entityA. Jar X
> persistence unit should be able to persist entityC and its collection of
> entityA, entityB.. etc
> Features:
> 1. Auto-classpath scanning (perhaps for persistence-fragment.xml.. then
> enumerate)
> 2. Support manual registration and unregistration of entity classes (not just
> class names) to support OSGi environments that have per-bundle classloaders
> and deploy/undeploy support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
