| Birt in JBoss [message #22332] |
Wed, 23 March 2005 09:56  |
Eclipse User |
|
|
|
Originally posted by: mbatchelor.no_s_p_a_m.pentaho.com
Hey all,
I'm trying to get the viewer running inside JBoss. What I did is took the
viewer deployment from birt, and copied it over to my JBoss deploy directory
as viewer.war.
JBoss starts, but when I attempt to view a report, I get the following
exceptions:
I'm attempting to view the report with the following URL:
http://localhost/viewer/engineservlet?__uri=d:\TestReport.rp tdesign&__format=pdf
09:42:28,093 ERROR [ServerPlatform] load plugin
D:\jboss-4.0.1sp1\server\default\deploy\viewer.war\WEB-INF\p lugins\drivers
failed
09:42:29,015 ERROR [Engine] StandardWrapperValve[ViewerServlet]:
Servlet.service() for servlet ViewerServlet threw exception
java.lang.NoSuchMethodError:
org.mozilla.javascript.Context.initStandardObjects()Lorg/moz illa/javascript/
ScriptableObject;
at
org.eclipse.birt.core.script.ScriptContext.<init>(ScriptContext.java:58)
at
org.eclipse.birt.report.engine.executor.ExecutionContext.<init >(ExecutionCon
text.java:103)
at
org.eclipse.birt.report.engine.impl.ReportHandle.execute(Rep ortHandle.java:1
95)
at
org.eclipse.birt.report.engine.impl.EmbeddedReportHandle.vie wReport(Embedded
ReportHandle.java:71)
at
org.eclipse.birt.report.viewer.aggregation.EngineFragment.do Service(Unknown
Source)
at
org.eclipse.birt.report.viewer.aggregation.RootFragment.serv ice(Unknown
Source)
at
org.eclipse.birt.report.viewer.servlets.ViewerServlet.doPost (Unknown Source)
at
org.eclipse.birt.report.viewer.servlets.ViewerServlet.doGet( Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(Application
FilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterCh
ain.java:157)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Repl yHeaderFilter.ja
va:75)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(Application
FilterChain.java:186)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterCh
ain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.ja
va:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal (StandardContext
Valve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.ja
va:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:104)
at
org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(Cu stomPrincipalVal
ve.java:66)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:102)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invok e(SecurityAssoci
ationValve.java:150)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:102)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCo ntextValve.java:
54)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:137
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(Sta ndardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase. java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapte r.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHand ler.processConne
ction(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndp oint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.jav
a:683)
at java.lang.Thread.run(Thread.java:534)
|
|
|
|
|
| Re: Birt in JBoss [message #25871 is a reply to message #25265] |
Mon, 11 April 2005 19:47  |
| Eclipse User |
|
|
|
Thanks for the head's up. I've filed an issue with the team asking them to
upgrade to a newer Rhino. I believe that they looked at an upgrade at one
point, but there may have been an issue with compatibility with Jakarta BSF
(Bean Scripting Framework). In any event, I've asked them to take another
look.
Thanks also for the info on JBoss. I'll add this info to the BIRT website so
that others can benefit from your experience.
- Paul
Paul Rogers
BIRT PMC
"jdixon" <jdixon@pentaho.com> wrote in message
news:d32aj1$qo9$1@news.eclipse.org...
>
> I was able to get the viewer working in JBoss by putting BIRT's js.jar in
> JBoss's server/default/lib. However the version of rhino that BIRT is
> using is over a year old (seems to be somewhere between Mozilla 1.0.2 and
> Mozilla 1.4, not sure because that version of js.jar is no longer
> downloadable.
>
> BIRT is not able to use the current version of js.jar due to its use of
> org.mozilla.javascript.IdFunction and org,mozilla.javascript.IdScriptable
> which, if I understand correctly, are not part of the public API.
>
> "Stanley Wang" <swang@actuate.com> wrote in message
> news:9949822fe13709f7beaba11223a6789f$1@www.eclipse.org...
>> Marc,
>>
>> We currently are testing viewer in an environment other than report
>> preview. The message
>> " D:\jboss-4.0.1sp1\server\default\deploy\viewer.war\WEB-INF\p lugins\drivers "
>> does not signal a real problem. From the stack, it seems that the Rhino
>> Javascript engine jar file (js.jar) is not reachable. For the short term,
>> try to put the jar file at a location that the app server can find.
>> Hope this helps.
>> Stanley Wang
>> BIRT Engine
>>
>>
>>
>>
>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05566 seconds
Home