[ https://issues.apache.org/jira/browse/OPENJPA-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737235#comment-16737235 ]
Romain Manni-Bucau commented on OPENJPA-2766: --------------------------------------------- Well the issue is that doing it at runtime requires a whiteboard pattern. Said in another manner you still need to facade the actual entity manager to add the classes to a new config, create the emf then switch it over. This is something very specific to OSGi behavior and in the regard of the OSGi integration code needed I don't think adding it in OpenJPA is worth it (you already have the addManagedClass API, even in the spec). Do you see something which would bring enough value there? > 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)