[
https://issues.apache.org/jira/browse/OPENJPA-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736731#comment-16736731
]
Matt Pavlovich commented on OPENJPA-2766:
-----------------------------------------
Hi [~romain.manni-bucau] jar-file handling requires all jars to be named at
compile time (ie.. allowing a 3rd party to extend an entity.. then add the jar
into the runtime and have it be supported)
I put together an example and posted it to GitHub. For simplicity, I've added
all the model-[a,b,c] jars into the same project. However, for the purposes of
the feature request, consider that they are _not_ known at build time. How
would this be supported by OpenJPA?
reference sample project: https://github.com/mattrpav/jpa-modular
Thanks!
> 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)
