Bug 292312 - JPA test on WebLogic should use filtered classloader instead of overwrote eclipselink.jar within WLS
Summary: JPA test on WebLogic should use filtered classloader instead of overwrote ecl...
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2009-10-14 16:22 EDT by Kevin Yuan CLA
Modified: 2022-06-09 10:22 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Yuan CLA 2009-10-14 16:22:50 EDT 
Currently all our JPA testing on WLS always overwrite org.eclipse.persistence_*.jar under %WLS_HOME%\modules using the latest eclipselink.jar in order to run existing JPA server testing on latest eclipselink.jar. But this configuration will affect other component which dependent on eclipselink.jar within WLS. Just like the suggestion from PM:

There are 2 options available to allow updates to EclipseLink library within WebLogic:

   1. Using SmartUpdate a set of modified classes are applied to the EclipseLink library.
   2. Applications use a more recent version of EclipseLink packaged within their applications and configuration for the filtered classloader (weblogic-application.xml in EAR) 

So the best way for our existing automation testing is "adding eclipselink.jar into application ear and configure the filtered classloader using weblogic-application.xml in EAR".
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:16:08 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:22:41 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink