|Re: BIRT 3.7.2 or later version working on WebSphere 8 [message #1053499 is a reply to message #1053132]
||Mon, 06 May 2013 06:04
| donino donino
Registered: July 2011
Is your BIRT runtime embedded in the portlet scope (in WEB-INF/lib folder), or in a shared folder of websphere? If it is shared, you could try to put it within WEB-INF/lib to limit possible side-effects and conflicts. I know it is not very smart, in particular when we want to restart the webapp, but it often resolves issues.
If you already tried this, i also encountered this issue with eXo, i was able to solve it on jBoss7 by creating a specific module dependency for the BIRT runtime. iI don't know if websphere 8 implemements something like module dependency?
[Updated on: Mon, 06 May 2013 06:05]
Report message to a moderator
|Re: BIRT 3.7.2 or later version working on WebSphere 8 [message #1160759 is a reply to message #1053499]
||Tue, 29 October 2013 06:33
| Prasanna Mondkar
Registered: October 2013
Hi Howard Yeung,|
I had exactly the same error as yours. I am using BIRT 3.7.2 and IBM WAS 8.5
With reference to the bug detailed below,
I added the following line before the Platform.startup(..) call
After this, BIRT reports are working fine.
I'm doubtful, as to whether this will break anything in WAS's runtime or not. BIRT's Platform start-up does set a Registry Provider, so i guess that should be fine. The only concern here is maybe the Provider set by BIRT may not be compatible with what WAS wants. Experts, please help me here ...
Also, Please have a look at the following bug as well,
This is the actual bug, occurs, when Platform restart is attempted.
But, in our case, WAS runtime has started the Platform, with the RegistryProvider set by it.
Here, the problem is more of BIRT runtime not re-using (or does not wants to / cannot re-use) a Registry Provider if already set. Maybe, it needs its own version.
I'm not sure of the solution i have used.
Experts, please guide ...
Powered by FUDForum
. Page generated in 0.01693 seconds