|
Re: [BIRT2.2RC0 Deployment] BEA Weblogic 8.1.x [message #243190 is a reply to message #243091] |
Mon, 18 June 2007 22:12 |
Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Chris,
Can you post the stacktrace? Also have you tried this with RC2 or 3?
Please log a bugzilla entry as well.
BTW, I would be interested in understanding where you found pain points
in using BIRT. We are beginning post 2.2 planning and anything we can
do to make the BIRT experience more pleasant is worth considering.
Thanks
Jason
chris wrote:
> Hi there,
>
> i experienced birt during the last three month, there were a lot of
> downs and also a few highlights ;)
> finally my framework works quite allright on a tomcat and also on a sun
> appserver...
> but today after the presentation my boss decided TO CHANGE TO A BEA
> WEBLOGIC PLATFORM!
>
> i went through the newsgroups and found some known bugs using this
> webserver.. and after a lot of trying a finally got my framework
> deployed without getting any exceptions.
>
> i figured out, that the following jar
>
> org.eclipse.equinox.registry_3.3.0.v20070416.jar
>
> causes the java.lang.StringIndexOutOfBoundsException.
>
> so now my questions:
> 1. are there any experiences in working with birt2.2rc0 on a weblogic?
> 2. will this bug be fixed in the 2.2 release?
> or:
> is there no light at the end of the tunnel and so i have to persuade my
> boss to use a tomcat?
>
> greetings,
> chris from munich
>
|
|
|
|
|
|
Re: [BIRT2.2RC0 Deployment] BEA Weblogic 8.1.x [message #243346 is a reply to message #243284] |
Tue, 19 June 2007 15:57 |
Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Chris,
Thanks for the responses. We will look into the bug.
Jason
Chris wrote:
> i forgot to mention the exception of the viewerServlet:
> ------------------------------------------------------------ ------------------
>
> org.eclipse.birt.report.exception.ViewerException: Fatal error occurred
> when try to startup report engine.
> at
> org.eclipse.birt.report.service.ReportEngineService.setEngin eContext(Unknown
> Source)
> at
> org.eclipse.birt.report.service.BirtViewerReportService.setC ontext(Unknown
> Source)
> at
> org.eclipse.birt.report.servlet.ViewerServlet.__getContext(U nknown Source)
> at
> org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer vlet.doGet(Unknown
> Source)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at
> org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
>
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
> weblogic.servlet.internal.ServletStubImpl$ServletInvocationA ction.run(ServletStubImpl.java:971)
>
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(Serv letStubImpl.java:402)
>
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(Serv letStubImpl.java:305)
>
> at
> weblogic.servlet.internal.WebAppServletContext$ServletInvoca tionAction.run(WebAppServletContext.java:6350)
>
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(Aut henticatedSubject.java:317)
>
> at
> weblogic.security.service.SecurityManager.runAs(SecurityMana ger.java:118)
> at
> weblogic.servlet.internal.WebAppServletContext.invokeServlet (WebAppServletContext.java:3635)
>
> at
> weblogic.servlet.internal.ServletRequestImpl.execute(Servlet RequestImpl.java:2585)
>
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197 )
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> ------------------------------------------------------------ ------------------
>
>
> maybe it could be related to this bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=136818
>
|
|
|
Powered by
FUDForum. Page generated in 0.03461 seconds