Kp,
At the risk of hijacking your thread - I would like to add some
specificity to your question..i.e.
let's say I want to create two separate JAR projects, each has their
own set of entities and persistence unit and, in fact, separate
persistence.xml. Will this work in a webapp when both resulting jars
are added to the WAR's WEB-INF/lib? Or must you only have a single
persistence.xml in a given webapp and must implement some merging
process in the build script?
Thanks,
-Chris
On Mon, Mar 18, 2013 at 9:55 AM, Krishnaprasad Subbarao
<[email protected]> wrote:
> Hello,
>
> I am working on a large application which has around 50 entities and many
> relational tables. We wish to use OpenJPA 2.1 as a Persistence provider.
>
> I would like to know what criteria's should be considered while deciding
> the number of persistence units to be defined in an application. Following
> are my questions about persistence units
>
> 1) What are points to be considered to decide how many persistence units
> should be created in an application?
>
> 2) Is it recommended to have one persistence unit per logical module
> (Business module) in an application?
>
> While exploring I found that multiple persistence units are created mostly
> if different entities are packaged in different WAR/JAR/EAR files. Is this
> the only criteria to have multiple units?
>
> Regards,
>
> Krishnaprasad (Kp)
>
