Community
Participate
Working Groups
Build Identifier: BIRT 2.5.2 We are trying to deploy the Web Viewer in a highly security-restricted WebSphere environment that does not allow setContextClassLoader(). Since setContextClassLoader() is called in a number of places within BIRT, we are effectively prevented from using BIRT in WebSphere. A quick scan of the source reveals 27 references in 12 classes scattered about the following packages * org.eclipse.birt.core * org.eclipse.birt.report.engine * org.eclipse.birt.report.viewer as well as some in UI components, which aren't a conflict for us. I posted the above as a question on the Community Forums site (http://www.eclipse.org/forums/index.php?t=msg&th=168802&start=0&) and was asked to submit a bug, so here it is. Reproducible: Always
Set version, added keywords
BIRT must invoke the setContextClassLoader to set the class loader as BIRT is running in the OSGi framework.
@wei yan: I'm not sure I understand. Are you saying that all of OSGi and BIRT are fundamentally incompatible with a high-security container that disallows setContextClassLoader()?
Correct.
See comment 2.
*** Bug 328025 has been marked as a duplicate of this bug. ***