| error in drilldown-report [message #244753] |
Tue, 26 June 2007 01:32  |
Eclipse User |
|
|
|
Originally posted by: kurt.knippschilds.de
Hi,
i have installed Birt 2.2RC2 and Birt 2.2RC3.
My Reports have a JDBC-Datasource and the datasource are in a library.
In the first Report there is a hyperlink to the second Report.
In the preview i can click on the hyperlink in the first row and i see the
second report and all things are ok.
But whe i click on hyperlinks in the other rows i have allways this error:
The following items have errors:
ReportDesign (id = 1):
- Cannot open the connection for the driver:
org.eclipse.birt.report.data.oda.jdbc
Missing properties in Connection.open(Properties).
Cannot open the connection for the driver:
org.eclipse.birt.report.data.oda.jdbcMissing properties in
Connection.open(Properties). ( 1 time(s) )
detail : org.eclipse.birt.report.data.adapter.api.AdapterException: Cannot
open the connection for the driver:
org.eclipse.birt.report.data.oda.jdbcMissing properties in
Connection.open(Properties). at
org.eclipse.birt.report.data.adapter.impl.DataRequestSession Impl.execute(DataRequestSessionImpl.java:426)
at
org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExec uteQuery(DteDataEngine.java:149)
at
org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExec uteQuery(DteDataEngine.java:115)
at
org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.e xecute(AbstractDataEngine.java:178)
at
org.eclipse.birt.report.engine.executor.ExecutionContext.exe cuteQuery(ExecutionContext.java:1669)
at
org.eclipse.birt.report.engine.executor.QueryItemExecutor.ex ecuteQuery(QueryItemExecutor.java:82)
at
org.eclipse.birt.report.engine.executor.TableItemExecutor.ex ecute(TableItemExecutor.java:61)
at
org.eclipse.birt.report.engine.internal.executor.wrap.Wrappe dReportItemExecutor.execute(WrappedReportItemExecutor.java:4 5)
at
org.eclipse.birt.report.engine.internal.executor.dup.Suppres sDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor .java:42)
at
org.eclipse.birt.report.engine.internal.executor.wrap.Wrappe dReportItemExecutor.execute(WrappedReportItemExecutor.java:4 5)
at
org.eclipse.birt.report.engine.internal.executor.l18n.Locali zedReportItemExecutor.execute(LocalizedReportItemExecutor.ja va:33)
at
org.eclipse.birt.report.engine.layout.html.HTMLBlockStacking LM.layoutChildren(HTMLBlockStackingLM.java:63)
at
org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.la yout(HTMLAbstractLM.java:171)
at
org.eclipse.birt.report.engine.layout.html.HTMLInlineStackin gLM.resumeLayout(HTMLInlineStackingLM.java:94)
at
org.eclipse.birt.report.engine.layout.html.HTMLInlineStackin gLM.layoutChildren(HTMLInlineStackingLM.java:138)
at
org.eclipse.birt.report.engine.layout.html.HTMLRowLM.layoutC hildren(HTMLRowLM.java:41)
at
org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.la yout(HTMLAbstractLM.java:171)
at
org.eclipse.birt.report.engine.layout.html.HTMLRowLM.layout( HTMLRowLM.java:31)
at
org.eclipse.birt.report.engine.layout.html.HTMLBlockStacking LM.layoutChildren(HTMLBlockStackingLM.java:68)
at
org.eclipse.birt.report.engine.layout.html.HTMLTableLM.layou tChildren(HTMLTableLM.java:81)
at
org.eclipse.birt.report.engine.layout.html.HTMLAbstractLM.la yout(HTMLAbstractLM.java:171)
at
org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout Children(HTMLPageLM.java:142)
at
org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout (HTMLPageLM.java:84)
at
org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutE ngine.layout(HTMLReportLayoutEngine.java:90)
at
org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doR un(RunAndRenderTask.java:148)
at
org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run (RunAndRenderTask.java:71)
at
org.eclipse.birt.report.service.ReportEngineService.runAndRe nderReport(Unknown
Source) at
org.eclipse.birt.report.service.ReportEngineService.runAndRe nderReport(Unknown
Source) at
org.eclipse.birt.report.service.BirtViewerReportService.runA ndRenderReport(Unknown
Source) at
org.eclipse.birt.report.service.actionhandler.BirtGetPageAll ActionHandler.__execute(Unknown
Source) at
org.eclipse.birt.report.service.actionhandler.AbstractBaseAc tionHandler.execute(Unknown
Source) at
org.eclipse.birt.report.soapengine.processor.AbstractBaseDoc umentProcessor.__executeAction(Unknown
Source) at
org.eclipse.birt.report.soapengine.processor.AbstractBaseCom ponentProcessor.executeAction(Unknown
Source) at
org.eclipse.birt.report.soapengine.processor.BirtDocumentPro cessor.handleGetPageAll(Unknown
Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
java.lang.reflect.Method.invoke(Unknown Source) at
org.eclipse.birt.report.soapengine.processor.AbstractBaseCom ponentProcessor.process(Unknown
Source) at
org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingI mpl.getUpdatedObjects(Unknown
Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
java.lang.reflect.Method.invoke(Unknown Source) at
org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCP rovider.java:397)
at
org.apache.axis.providers.java.RPCProvider.processMessage(RP CProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvi der.java:323)
at
org.apache.axis.strategies.InvocationStrategy.visit(Invocati onStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at
org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService .java:453) at
org.apache.axis.server.AxisServer.invoke(AxisServer.java:281 ) at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServle t.java:699) at
org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherSer vlet.doPost(Unknown
Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
org.apache.axis.transport.http.AxisServletBase.service(AxisS ervletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase. java:995) at
org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.CertificatesValve.invoke(Certific atesValve.java:246)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase. java:995) at
org.apache.catalina.core.StandardContext.invoke(StandardCont ext.java:2422)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(Error DispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:641)
at
org.eclipse.tomcat.internal.EclipseErrorReportValve.invoke(E clipseErrorReportValve.java:153)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase. java:995) at
org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineVa lveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPip eline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase. java:995) at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapte r.java:199) at
org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:828)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHand ler.processConnection(Http11Protocol.java:700)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndp oint.java:584)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.ru n(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
Whats wrong?
Thanks Kurt
|
|
|
|
|
|
|
|
|
|
| Re: error in drilldown-report [message #247668 is a reply to message #247475] |
Thu, 12 July 2007 13:45  |
| Eclipse User |
|
|
|
Originally posted by: rermish.carreker.com
The reports do not run in a seperate server environment. I am running them
in the Eclipse Report Designer (birt-report-designer-all-in-one-2_2_0). The
only change that I have made to the shipped configuration is to add DB2 jdbc
drivers and import the reports into a report project. The reports run fine
when I execute them directly, but when I drill down into a report that has
dynamic parameters, the parameter list is not populated from the database
and it throws a javascript error in BirtParameterDialog.js at
var tempText = oSEC[0].options[oSEC[0].selectedIndex].text;
However, as I said, the same reports, with the library in the same relative
location, run just fine on Websphere with the 2.2 runtime, and the reports
will run just fine in the Report Designer when I execute the reports
directly using preview or running in a browser. So the Report Designer is
for sure finding the library datasource when when the reports are executed
directly. This leads me to believe that it is not a problem with the
location of the library.
"qwang" <qwang@actuate.com> wrote in message
news:f73nhn$dqt$1@build.eclipse.org...
> Rod Ermish wrote:
>> I am experiencing the same problem using 2.2 and a library data source in
>> the Report Designer. The reports that are giving me problems are those
>> with dynamic parameters. The parameter list does not seem to be populated
>> when I drill through from another report. However, when I deploy those
>> same reports on Websphere where I have installed the 2.2 runtime, the
>> reports run fine.
>> Rod
>>
>> "qwang" <qwang@actuate.com> wrote in message
>> news:f6hdlo$jlp$1@build.eclipse.org...
>>> news.eclipse.birt wrote:
>>>> Hi,
>>>>
>>>> when i change the Datasource from Library to a Datasource direct in the
>>>> report, then the Drilldown works.
>>>> Must i configure specially the path to the Library or what is wrong?
>>>>
>>>> Thanks Kurt
>>>>
>>>> "shaik" <sjaheer@gmail.com> schrieb im Newsbeitrag
>>>> news:eb2882e4ff42670fad0d257dab7bf5b9$1@www.eclipse.org...
>>>>> Hello,
>>>>>
>>>>> It seems the problem with second report which u r calling in first
>>>>> report,
>>>>> and when u click link in first row u said that its executing the
>>>>> subreport and while u clicking in second line its giving error right,
>>>>> its because of the connection in second report is still opened and
>>>>> when u cling in second row it wil try to create a new connection again
>>>>> and then it may throwing the error.
>>>>>
>>>>> so better u write code to close the connection at end in the second
>>>>> report after executing it.
>>>>>
>>>>> it may be solve the issue.
>>>>>
>>>>
>>> could you attached the report file?
>>
>>
> Do these reports run in a separate server environment? If it's in a
> separate server environment, you'd make sure the library is in the right
> resource folder to let it work.
>
> Thanks
> Qs
|
|
|
| Re: error in drilldown-report [message #249364 is a reply to message #247668] |
Mon, 23 July 2007 06:44 |
| Eclipse User |
|
|
|
Could you provide the files?
Thanks
Qiangsheng
Rod Ermish wrote:
> The reports do not run in a seperate server environment. I am running them
> in the Eclipse Report Designer (birt-report-designer-all-in-one-2_2_0). The
> only change that I have made to the shipped configuration is to add DB2 jdbc
> drivers and import the reports into a report project. The reports run fine
> when I execute them directly, but when I drill down into a report that has
> dynamic parameters, the parameter list is not populated from the database
> and it throws a javascript error in BirtParameterDialog.js at
> var tempText = oSEC[0].options[oSEC[0].selectedIndex].text;
>
> However, as I said, the same reports, with the library in the same relative
> location, run just fine on Websphere with the 2.2 runtime, and the reports
> will run just fine in the Report Designer when I execute the reports
> directly using preview or running in a browser. So the Report Designer is
> for sure finding the library datasource when when the reports are executed
> directly. This leads me to believe that it is not a problem with the
> location of the library.
>
> "qwang" <qwang@actuate.com> wrote in message
> news:f73nhn$dqt$1@build.eclipse.org...
>
>> Rod Ermish wrote:
>>> I am experiencing the same problem using 2.2 and a library data source in
>>> the Report Designer. The reports that are giving me problems are those
>>> with dynamic parameters. The parameter list does not seem to be populated
>>> when I drill through from another report. However, when I deploy those
>>> same reports on Websphere where I have installed the 2.2 runtime, the
>>> reports run fine.
>>> Rod
>>>
>>> "qwang" <qwang@actuate.com> wrote in message
>>> news:f6hdlo$jlp$1@build.eclipse.org...
>>>> news.eclipse.birt wrote:
>>>>> Hi,
>>>>>
>>>>> when i change the Datasource from Library to a Datasource direct in the
>>>>> report, then the Drilldown works.
>>>>> Must i configure specially the path to the Library or what is wrong?
>>>>>
>>>>> Thanks Kurt
>>>>>
>>>>> "shaik" <sjaheer@gmail.com> schrieb im Newsbeitrag
>>>>> news:eb2882e4ff42670fad0d257dab7bf5b9$1@www.eclipse.org...
>>>>>> Hello,
>>>>>>
>>>>>> It seems the problem with second report which u r calling in first
>>>>>> report,
>>>>>> and when u click link in first row u said that its executing the
>>>>>> subreport and while u clicking in second line its giving error right,
>>>>>> its because of the connection in second report is still opened and
>>>>>> when u cling in second row it wil try to create a new connection again
>>>>>> and then it may throwing the error.
>>>>>>
>>>>>> so better u write code to close the connection at end in the second
>>>>>> report after executing it.
>>>>>>
>>>>>> it may be solve the issue.
>>>>>>
>>>> could you attached the report file?
>>>
>> Do these reports run in a separate server environment? If it's in a
>> separate server environment, you'd make sure the library is in the right
>> resource folder to let it work.
>>
>> Thanks
>> Qs
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02925 seconds
Home