Mark, The resolution scope is per persistent unit. So the issue is not about OpenJPA libraries being used with same x.y.z.Customer class packaged in separate war/ear. The question is how likely that two classes having the same fully-qualified class name or using same alias but loaded by two different classloaders are being used in a *single* persistence unit defined in a *single* persistence.xml?
----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/Classloading-needs-to-be-refurbished-tp6859197p6862275.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
