> Has anyone successfully used this with OpenJPA to avoid using the one
provided by WebLogic? 

Uh, we are (in DEV), and AFAIK it works... Can you elaborate on "I know
that this doesn't work 100% of the time" ??


-----Original Message-----
From: KARR, DAVID (ATTCINW) [mailto:dk0...@att.com] 
Sent: Wednesday, December 02, 2009 7:30 AM
To: users@openjpa.apache.org
Subject: RE: Using latest OpenJPA in WebLogic 10

> -----Original Message-----
> From: Ravi Palacherla [mailto:ravi.palache...@oracle.com]
> Sent: Tuesday, December 01, 2009 7:00 PM
> To: users@openjpa.apache.org
> Subject: RE: Using latest OpenJPA in WebLogic 10
> 
> Hi David,
> 
> You can use Filtering Classloader that weblogic server supports.

Yes, using the "prefer-application-packages" element in the
weblogic-application.xml file.  I'm familiar with that.  The problem is,
I know that this doesn't work 100% of the time.  Has anyone successfully
used this with OpenJPA to avoid using the one provided by WebLogic?

> -----Original Message-----
> From: KARR, DAVID (ATTCINW) [mailto:dk0...@att.com]
> Sent: Tuesday, December 01, 2009 6:41 PM
> To: users@openjpa.apache.org
> Subject: Using latest OpenJPA in WebLogic 10
> 
> I'm looking at using the latest GA release of OpenJPA, v1.2.1, on 
> WebLogic 10 (not 10.3), in a webapp, not as an ejb-jar or EAR.
> Apparently WebLogic 10 already includes a version of OpenJPA, but 
> certainly an older version.  Will I have any trouble using the latest 
> OpenJPA just in my webapp?  Is there something I need to do to prevent

> conflicts?  I'm familiar with "prefer-web-inf-classes", but I'm not 
> sure whether that will help.

____________________________________________________________

• This email and any files transmitted with it are CONFIDENTIAL and intended
  solely for the use of the individual or entity to which they are addressed.
• Any unauthorized copying, disclosure, or distribution of the material within
  this email is strictly forbidden.
• Any views or opinions presented within this e-mail are solely those of the
  author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
• An electronic message is not binding on its sender. Any message referring to
  a binding engagement must be confirmed in writing and duly signed.
• If you have received this email in error, please notify the sender immediately
  and delete the original.

Reply via email to