Yes, imo we need to support such use cases. Take as an example geronimo where OpenJPA is pretty much at the very bottom of the ClassLoader hierarchy and shared by multiple EARs and WARs.
Then think about some multi-tenant setup where different WARs (1 per tenant) use the same core-backend.jar (maybe even different versions) which contains JPA entities for some basic stuff (Customer, User, ..) I guess this would require exactly this scenario. LieGrue, strub ----- Original Message ----- > From: Pinaki Poddar <[email protected]> > To: [email protected] > Cc: > Sent: Tuesday, October 4, 2011 7:24 PM > Subject: Re: Classloading needs to be refurbished? > > A lot of complexity in persistent domain classloading is designed to address > a rather unusual scenario : > the same persistence unit using multiple classes of the same fully-qualified > name but loaded with different classloaders. > Is that really worth supporting at the cost of so much complexity? > > ----- > Pinaki Poddar > Chair, Apache OpenJPA Project > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Classloading-needs-to-be-refurbished-tp6859197p6859422.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. >
