openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Boblitz John <John.Bobl...@BERTSCHI.com>
Subject AW: pro & contra of using Multiple Persistence Units
Date Fri, 18 May 2012 06:28:42 GMT
 

> -----Ursprüngliche Nachricht-----
> Von: Boblitz John [mailto:John.Boblitz@BERTSCHI.com] 
> Gesendet: Montag, 14. Mai 2012 15:07
> An: 'users@openjpa.apache.org'
> Betreff: pro & contra of using Multiple Persistence Units
> 
> Good Afternoon,
>  
> I have been looking around the interwebs but can't seem to 
> find any discussions regarding the advantages / disadvantages 
> of using multiple persistence units in a Java SE environment 
> to connect to a single data source.
>  
> Does anyone know of a good link?
>  
> Also, any info/recomendations from the community would be great ...
>  
> A bit of Background:
>  
> I am currently working on an application which splits it's 
> functionality across several services, mainly based on the 
> function of the data (basic code tables, product data, 
> employee data, etc ...) and / or an sub-application 
> (Invoicing, etc ...).
>  
> Each of the services will obviously need to access data from 
> other services, and it is currently designed that each 
> service has it's own Persistence Unit.  IOW, basic code 
> tables are "managed" in packaged service with it's own 
> persistence implementation/unit JAR.
>  
> I am a bit concerned that the various PU's will end up with 
> divergent states of the data, unless they can somehow be synchronized.
>  
> So, what I'm looking for is any information to help me decide 
> how to best configure the persistence unit(s).
>  
>  
> Thanks & Best Regards
>  
>  
>  
> 
> John Boblitz
> 
> ---- 
> 
> Who is General Failure, and why is he reading my hard disk?
> 
> 

One time push of my previous post, in the hopes that it was simply overseen.  I will not do
so again.

John
Mime
View raw message