Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 328025

Summary: default class loader policies when deploying BIRT 2.5.1 on Websphere 7.0
Product: z_Archived Reporter: Anthony Farrell <afarrell>
Component: BIRTAssignee: Birt-ReportEngine-inbox <Birt-ReportEngine-inbox>
Status: CLOSED DUPLICATE QA Contact: Xiaoying Gu <bluesoldier>
Severity: normal    
Priority: P3 CC: bluesoldier
Version: unspecified   
Target Milestone: 3.7.0   
Hardware: PC   
OS: Windows XP   
Whiteboard: Obsolete

Description Anthony Farrell CLA 2010-10-18 06:00:02 EDT 
Build Identifier: Build id: 20090920-1017

The following represent the default settings for the class loader policies when deploying BIRT 2.5.1 on Websphere 7.0 to :
1) parent last AND
2) single class loader for application

I get an error "can't start report engine". Should BIRT deploy and run with 1 and 2 set as above?


If I change either one (change to parent class loader first OR multiple class loaders for application) BIRT deploys and runs.

for my deployment I am going with a setting of "parent last" and "multiple class loaders for application". 

We have modified out deployment process to change the default settings, it would be much more convient if BIRT worked with the default WAS settings.

Reproducible: Always

Steps to Reproduce:
The BIRT viewer is packaged as a war and wraped in an EAR and deployed to websphere.
Comment 1 Xiaoying Gu CLA 2010-11-17 03:26:35 EST 
The class loader order has to be change to Classes loaded with local class loader first (parent last) for running birt runtime on Websphere, which is not the default setting.
Please see comment: https://bugs.eclipse.org/bugs/show_bug.cgi?id=314373#c2

Set as duplicated.

*** This bug has been marked as a duplicate of bug 314373 ***