Eclipse Community Forums: BIRT » setContextClassLoader() and WebSphere deployment

Help

Home

Home » Archived » BIRT » setContextClassLoader() and WebSphere deployment

Show: Today's Messages :: Show Polls :: Message Navigator

setContextClassLoader() and WebSphere deployment [message #535801]

Tue, 25 May 2010 17:29

Jim Garrison

Messages: 57
Registered: July 2009

Member

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.

Is there a solution to this problem other than relaxing the security constraints?

[Updated on: Tue, 25 May 2010 17:43]

Report message to a moderator

Re: setContextClassLoader() and WebSphere deployment [message #535834 is a reply to message #535801]

Tue, 25 May 2010 22:15

Jason Weathersby

Messages: 9167
Registered: July 2009

Senior Member

Jim,

Can you open a bugzilla entry for this?

Jason

On 5/25/2010 1:29 PM, Jim Garrison wrote:
> 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 references in
> * 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.
>
> Is there a solution to this problem other than relaxing the security
> constraints?

Report message to a moderator