"dataSetRow" is not defined [message #368633] |
Tue, 16 June 2009 12:00  |
Eclipse User |
|
|
|
Originally posted by: hoe.zurich.ibm.com
I'm running into the following error (with BIRT 2.3.0 engine). Who knows
how to resolve this? (BTW, I'm using a report design that has an EMF
Data Source/Set with a Row Mapping, and a Column Mapping "name" defined).
Many thanks,
Christian
-- SNIP
org.eclipse.birt.report.engine.api.EngineException: There are errors
evaluating script "dataSetRow["name"]": ReferenceError: "dataSetRow" is
not defined. (<inline>#1)
at
org.eclipse.birt.report.engine.executor.ExecutionContext.add Exception(ExecutionContext.java:1121)
at
org.eclipse.birt.report.engine.executor.ExecutionContext.add Exception(ExecutionContext.java:1085)
at
org.eclipse.birt.report.engine.executor.QueryItemExecutor.ex ecuteQuery(QueryItemExecutor.java:88)
at
org.eclipse.birt.report.engine.executor.TableItemExecutor.ex ecute(TableItemExecutor.java:62)
at
org.eclipse.birt.report.engine.internal.executor.dup.Suppres sDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor .java:43)
at
org.eclipse.birt.report.engine.internal.executor.wrap.Wrappe dReportItemExecutor.execute(WrappedReportItemExecutor.java:4 6)
at
org.eclipse.birt.report.engine.internal.executor.l18n.Locali zedReportItemExecutor.execute(LocalizedReportItemExecutor.ja va:34)
at
org.eclipse.birt.report.engine.layout.html.HTMLBlockStacking LM.layoutNodes(HTMLBlockStackingLM.java:64)
at
org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout (HTMLPageLM.java:90)
at
org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutE ngine.layout(HTMLReportLayoutEngine.java:99)
at
org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doR un(RunAndRenderTask.java:157)
at
org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run (RunAndRenderTask.java:70)
-- SNIP
|
|
|
|
|
|
Re: "dataSetRow" is not defined [message #368899 is a reply to message #368646] |
Fri, 03 July 2009 11:53   |
Eclipse User |
|
|
|
Originally posted by: hoe.zurich.ibm.com
Jason and Dear All,
I was busy with other things, but have now returned to this problem.
If I do a simple report with an EMF data source that's based on the
example library model (from org.eclipse.emf.examples.library) this works
fine.
I now suspect that the problem here might have to do with one of these
two causes:
(1) My meta-model, since its application-specific, does not reside in
an Eclipse plug-in (such as org.eclipse.emf.examples.library), but in a
plug-in project in the Eclipse workspace. There it defines extensions
org.eclipse.emf.ecore.generated_package as usual for EMF models, but
perhaps BIRT does not pick up these package registrations.
I've tried report generation also in a PDE environment (i.e. after Run
As / Eclipse Application), but that does not seem to make a difference.
(2) My model is currently split across two XMI files, again using
normal EMF conventions. I specify both as instance models in the EMF
data source.
I've tried to combine them into one, but that does not seem to make a
difference either.
Does (1) or (2) ring any further bells?
Thanks,
Christian
Jason Weathersby wrote:
> I have seen a similar error when the system has conflicting versions of
> Rhino.jar. Does the simple test report work in your environment? How
> are you deploying it?
>>> Christian Hoertnagl wrote:
>>>> I'm running into the following error (with BIRT 2.3.0 engine). Who
>>>> knows how to resolve this? (BTW, I'm using a report design that has
>>>> an EMF Data Source/Set with a Row Mapping, and a Column Mapping
>>>> "name" defined).
>>>> -- SNIP
>>>> org.eclipse.birt.report.engine.api.EngineException: There are errors
>>>> evaluating script "dataSetRow["name"]": ReferenceError: "dataSetRow"
>>>> is not defined. (<inline>#1)
>>>> at
>>>> org.eclipse.birt.report.engine.executor.ExecutionContext.add Exception(ExecutionContext.java:1121)
|
|
|
|
|
Re: "dataSetRow" is not defined [message #1798595 is a reply to message #368913] |
Tue, 20 November 2018 14:02  |
Eclipse User |
|
|
|
The answer is simple.
You have a redundant data_binding somewhere.
1. Look for the indicated ID in the error message then switch to XML_Source tab to find the element it's using.
2. Return back to the Layout and click Binding TAB under the Property Editor.
3. Remove redundant binding.
|
|
|
Powered by
FUDForum. Page generated in 0.04551 seconds