Skip to main content



      Home
Home » Archived » BIRT » Problem rendering a report with an xml file as a data source : truncated data text
Problem rendering a report with an xml file as a data source : truncated data text [message #152188] Mon, 10 April 2006 04:36 Go to next message
Eclipse UserFriend
Originally posted by: ludovic.chane-won-in.atosorigin.com

Hi all,
I have a problem when I render my birt report. Some data of my dataSet
is truncated !!!
My report consists in an xml data source and a simple dataSet. The
dataSet matches an xpath and collect some text. Those texts are more or
less long and after n rows (dataRows), the text of the n+1 dataRow is
truncated. Then, the following rows are okay but p rows after, my text
is truncated and ... etc
It seems to be a problem of cache memory. This problem appears not only
on the report but already in the previsualisation of the dataSet in
eclipse. Maybe, some dataSet parameters exist but I didn't find them.
The only relevant parameters I found were cachedMetaData and
cachedRowCount. I don't know how to use the cachedMetaData parameter and
the cachedRowCount parameter can't resolve my problem.

I'm lost, please help me ... and forgive me for my poor english
Regards,

Ludo


ps : i can join the complete log if you need it
found any issue? (I've got the same problem) [message #152858 is a reply to message #152188] Wed, 12 April 2006 04:43 Go to previous messageGo to next message
Eclipse UserFriend
Did you find any issue? (I've got the same problem)

Gilles
problem with & character (was Re: Problem rendering a report with an xml file as a data source : [message #152874 is a reply to message #152188] Wed, 12 April 2006 05:46 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: marc.leineweber.icc-gmbh.de

Hi Ludo,

I have a similar problem, the reason in my case is an & character in my text
(I use an XML data source, BIRT 2.0.1) - that character and the end of the
text of the field after that character are truncated. Even the & entity
does not work. Does your text contain an & and if yes, did you find a
workaround or solution to display this character?

Or does anybody else have seen this problem and may provide a solution?

Regards,

Marc


"Ludovic CWI" <ludovic.chane-won-in@atosorigin.com> schrieb im Newsbeitrag
news:e1d594$eq1$1@utils.eclipse.org...
> Hi all,
> I have a problem when I render my birt report. Some data of my dataSet is
> truncated !!!
> My report consists in an xml data source and a simple dataSet. The dataSet
> matches an xpath and collect some text. Those texts are more or less long
> and after n rows (dataRows), the text of the n+1 dataRow is truncated.
> Then, the following rows are okay but p rows after, my text is truncated
> and ... etc
> It seems to be a problem of cache memory. This problem appears not only on
> the report but already in the previsualisation of the dataSet in eclipse.
> Maybe, some dataSet parameters exist but I didn't find them. The only
> relevant parameters I found were cachedMetaData and cachedRowCount. I
> don't know how to use the cachedMetaData parameter and the cachedRowCount
> parameter can't resolve my problem.
>
> I'm lost, please help me ... and forgive me for my poor english
> Regards,
>
> Ludo
>
>
> ps : i can join the complete log if you need it
Re: problem with & character (was Re: Problem rendering a report with an xml file as a data sour [message #153159 is a reply to message #152874] Thu, 13 April 2006 03:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: marc.leineweber.icc-gmbh.de

Hi again,

the behavior I described (everything OK when no special character was in the
text) was shown for a small xml data source and with only one data set
defined. Now, with a more complex report and for that a bigger xml file, I
have the problem as you described it - even without any special character...
Did you find a solution yet? I would appreciate any hint.

Regards,

Marc

"Marc Leineweber" <marc.leineweber@icc-gmbh.de> schrieb im Newsbeitrag
news:e1ii92$41n$1@utils.eclipse.org...
> Hi Ludo,
>
> I have a similar problem, the reason in my case is an & character in my
> text (I use an XML data source, BIRT 2.0.1) - that character and the end
> of the text of the field after that character are truncated. Even the
> &amp; entity does not work. Does your text contain an & and if yes, did
> you find a workaround or solution to display this character?
>
> Or does anybody else have seen this problem and may provide a solution?
>
> Regards,
>
> Marc
>
>
> "Ludovic CWI" <ludovic.chane-won-in@atosorigin.com> schrieb im Newsbeitrag
> news:e1d594$eq1$1@utils.eclipse.org...
>> Hi all,
>> I have a problem when I render my birt report. Some data of my dataSet is
>> truncated !!!
>> My report consists in an xml data source and a simple dataSet. The
>> dataSet matches an xpath and collect some text. Those texts are more or
>> less long and after n rows (dataRows), the text of the n+1 dataRow is
>> truncated. Then, the following rows are okay but p rows after, my text is
>> truncated and ... etc
>> It seems to be a problem of cache memory. This problem appears not only
>> on the report but already in the previsualisation of the dataSet in
>> eclipse. Maybe, some dataSet parameters exist but I didn't find them. The
>> only relevant parameters I found were cachedMetaData and cachedRowCount.
>> I don't know how to use the cachedMetaData parameter and the
>> cachedRowCount parameter can't resolve my problem.
>>
>> I'm lost, please help me ... and forgive me for my poor english
>> Regards,
>>
>> Ludo
>>
>>
>> ps : i can join the complete log if you need it
>
>
Re: found any issue? (I've got the same problem) [message #153342 is a reply to message #152858] Thu, 13 April 2006 09:04 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ludovic.chane-won-in.atosorigin.com

Hi
I'm sorry, i'm still stuck ...
I will give you any hint if I solve the issue

regards,
Ludo

Gilles a écrit :
> Did you find any issue? (I've got the same problem)
>
> Gilles
>
Re: problem with & character (was Re: Problem rendering a report with an xml file as a data sour [message #153374 is a reply to message #153159] Thu, 13 April 2006 09:17 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ludovic.chane-won-in.atosorigin.com

Hi,

1.First for your problem of & character, you have to put your data
between CDATA brackets : <![CDATA[ blablabla & blablabla ]]> and it will
normally work.
2.I notice the same behaviour you mentionned "Now, with a more complex
report and for that a bigger xml file, I have the problem as you
described it - even without any special character..." but I did not
solve the problem yet. And I don't know how to do for now ... Please
community help us ! ^^

Here some parts of my log :
10 avr. 2006 10:16:50
org.eclipse.birt.data.engine.odaconsumer.PreparedStatement doSetProperty
WARNING: Cannot set statement property.
java.lang.UnsupportedOperationException: IQuery.setProperty( String
propertyName, String propertyValue )
at
org.eclipse.datatools.connectivity.oda.consumer.helper.OdaOb ject.handleUnsupportedOp(OdaObject.java:278)
at
org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQu ery.setProperty(OdaQuery.java:229)
at
org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.d oSetProperty(PreparedStatement.java:154)
at
org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.s etProperty(PreparedStatement.java:136)
at
org.eclipse.birt.data.engine.executor.DataSourceQuery.addPro perties(DataSourceQuery.java:348)
at
org.eclipse.birt.data.engine.executor.DataSourceQuery.prepar e(DataSourceQuery.java:303)
at
org.eclipse.birt.data.engine.impl.PreparedExtendedDSQuery$Ex tendedDSQueryExecutor.prepareOdiQuery(PreparedExtendedDSQuer y.java:277)
at
org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.pre pareExecution(PreparedQuery.java:672)
at
org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.acc ess$000(PreparedQuery.java:498)
at
org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(Pr eparedQuery.java:225)
at
org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.ex ecute(PreparedDataSourceQuery.java:145)
at
org.eclipse.birt.report.engine.data.dte.DteDataEngine.execut e(DteDataEngine.java:205)
at
org.eclipse.birt.report.engine.executor.QueryItemExecutor.op enResultSet(QueryItemExecutor.java:62)
at
org.eclipse.birt.report.engine.executor.TableItemExecutor.ex ecute(TableItemExecutor.java:122)
at
org.eclipse.birt.report.engine.executor.ReportExecutorVisito r.visitTableItem(ReportExecutorVisitor.java:187)
at
org.eclipse.birt.report.engine.ir.TableItemDesign.accept(Tab leItemDesign.java:69)
at
org.eclipse.birt.report.engine.executor.ReportExecutor.execu te(ReportExecutor.java:125)
at
org.eclipse.birt.report.engine.executor.ReportExecutor.execu te(ReportExecutor.java:89)
at
org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run (RunAndRenderTask.java:175)
at ExecuteReport.executeReport(ExecuteReport.java:84)
at ExecuteReport.main(ExecuteReport.java:100)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.ja va:202)
at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJav a.java:134)
at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178 )
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
10 avr. 2006 10:16:50
org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
INFO: memoryCacheRowCount is 20000
10 avr. 2006 10:16:51
org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
INFO: MemoryCache is used
10 avr. 2006 10:16:51
org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
INFO: Time consumed by cache is: 1 second

regards,

Ludo

Marc Leineweber a écrit :
> Hi again,
>
> the behavior I described (everything OK when no special character was in the
> text) was shown for a small xml data source and with only one data set
> defined. Now, with a more complex report and for that a bigger xml file, I
> have the problem as you described it - even without any special character...
> Did you find a solution yet? I would appreciate any hint.
>
> Regards,
>
> Marc
>
> "Marc Leineweber" <marc.leineweber@icc-gmbh.de> schrieb im Newsbeitrag
> news:e1ii92$41n$1@utils.eclipse.org...
>> Hi Ludo,
>>
>> I have a similar problem, the reason in my case is an & character in my
>> text (I use an XML data source, BIRT 2.0.1) - that character and the end
>> of the text of the field after that character are truncated. Even the
>> &amp; entity does not work. Does your text contain an & and if yes, did
>> you find a workaround or solution to display this character?
>>
>> Or does anybody else have seen this problem and may provide a solution?
>>
>> Regards,
>>
>> Marc
>>
>>
>> "Ludovic CWI" <ludovic.chane-won-in@atosorigin.com> schrieb im Newsbeitrag
>> news:e1d594$eq1$1@utils.eclipse.org...
>>> Hi all,
>>> I have a problem when I render my birt report. Some data of my dataSet is
>>> truncated !!!
>>> My report consists in an xml data source and a simple dataSet. The
>>> dataSet matches an xpath and collect some text. Those texts are more or
>>> less long and after n rows (dataRows), the text of the n+1 dataRow is
>>> truncated. Then, the following rows are okay but p rows after, my text is
>>> truncated and ... etc
>>> It seems to be a problem of cache memory. This problem appears not only
>>> on the report but already in the previsualisation of the dataSet in
>>> eclipse. Maybe, some dataSet parameters exist but I didn't find them. The
>>> only relevant parameters I found were cachedMetaData and cachedRowCount.
>>> I don't know how to use the cachedMetaData parameter and the
>>> cachedRowCount parameter can't resolve my problem.
>>>
>>> I'm lost, please help me ... and forgive me for my poor english
>>> Regards,
>>>
>>> Ludo
>>>
>>>
>>> ps : i can join the complete log if you need it
>>
>
>
Re: Problem rendering a report with an xml file as a data source : truncated data text [message #154034 is a reply to message #153374] Tue, 18 April 2006 04:26 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: marc.leineweber.icc-gmbh.de

Hi Ludovic,

thank you for the hint, the CDATA soultion works for the special character
problem. Though I have no general solution for the weird truncation problem
you described, I avoided the truncation by restructuring my XML data source:
I had a big level in my XML data tree with lots of attributes put into
simple nodes, plus some complex nodes (with subnodes) for my "subtables"; I
divided the big level into smaller portions by adding nodes to collect
attributes in them, and voil
Re: Problem rendering a report with an xml file as a data source : truncated data text [message #155698 is a reply to message #154034] Mon, 24 April 2006 09:14 Go to previous message
Eclipse UserFriend
Originally posted by: ludovic.chane-won-in.atosorigin.com

Hi Marc,
I didn't thoroughly understand your explanation but thanks to you I
managed to solve my problem. Actually, instead of putting my text into a
node, I put it into an attribute of that node. And it works. But I still
can't understand why there was a truncation before.
So maybe it's what you suggested me. In all cases, I'm very thankful to you.

Regards,

Ludovic

Marc Leineweber a écrit :
> Hi Ludovic,
>
> thank you for the hint, the CDATA soultion works for the special character
> problem. Though I have no general solution for the weird truncation problem
> you described, I avoided the truncation by restructuring my XML data source:
> I had a big level in my XML data tree with lots of attributes put into
> simple nodes, plus some complex nodes (with subnodes) for my "subtables"; I
> divided the big level into smaller portions by adding nodes to collect
> attributes in them, and voilà - it works without any truncation. May be the
> problem will come again when adding more data to the XML file, but I hope
> this approach will work even for more complex data sources.
>
> I got a (may be similar but) different hint from another newsgroup reader:
> He added new xml tags to move the truncation to this data which he does not
> need, but I did not test it for my case.
>
> I hope this is of at least little help, regards
>
> Marc
>
> "Ludovic CWI" <ludovic.chane-won-in@atosorigin.com> schrieb im Newsbeitrag
> news:e1lirn$jut$1@utils.eclipse.org...
>> Hi,
>>
>> 1.First for your problem of & character, you have to put your data between
>> CDATA brackets : <![CDATA[ blablabla & blablabla ]]> and it will normally
>> work.
>> 2.I notice the same behaviour you mentionned "Now, with a more complex
>> report and for that a bigger xml file, I have the problem as you described
>> it - even without any special character..." but I did not solve the
>> problem yet. And I don't know how to do for now ... Please community help
>> us ! ^^
>>
>> Here some parts of my log :
>> 10 avr. 2006 10:16:50
>> org.eclipse.birt.data.engine.odaconsumer.PreparedStatement doSetProperty
>> WARNING: Cannot set statement property.
>> java.lang.UnsupportedOperationException: IQuery.setProperty( String
>> propertyName, String propertyValue )
>> at
>> org.eclipse.datatools.connectivity.oda.consumer.helper.OdaOb ject.handleUnsupportedOp(OdaObject.java:278)
>> at
>> org.eclipse.datatools.connectivity.oda.consumer.helper.OdaQu ery.setProperty(OdaQuery.java:229)
>> at
>> org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.d oSetProperty(PreparedStatement.java:154)
>> at
>> org.eclipse.birt.data.engine.odaconsumer.PreparedStatement.s etProperty(PreparedStatement.java:136)
>> at
>> org.eclipse.birt.data.engine.executor.DataSourceQuery.addPro perties(DataSourceQuery.java:348)
>> at
>> org.eclipse.birt.data.engine.executor.DataSourceQuery.prepar e(DataSourceQuery.java:303)
>> at
>> org.eclipse.birt.data.engine.impl.PreparedExtendedDSQuery$Ex tendedDSQueryExecutor.prepareOdiQuery(PreparedExtendedDSQuer y.java:277)
>> at
>> org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.pre pareExecution(PreparedQuery.java:672)
>> at
>> org.eclipse.birt.data.engine.impl.PreparedQuery$Executor.acc ess$000(PreparedQuery.java:498)
>> at
>> org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(Pr eparedQuery.java:225)
>> at
>> org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.ex ecute(PreparedDataSourceQuery.java:145)
>> at
>> org.eclipse.birt.report.engine.data.dte.DteDataEngine.execut e(DteDataEngine.java:205)
>> at
>> org.eclipse.birt.report.engine.executor.QueryItemExecutor.op enResultSet(QueryItemExecutor.java:62)
>> at
>> org.eclipse.birt.report.engine.executor.TableItemExecutor.ex ecute(TableItemExecutor.java:122)
>> at
>> org.eclipse.birt.report.engine.executor.ReportExecutorVisito r.visitTableItem(ReportExecutorVisitor.java:187)
>> at
>> org.eclipse.birt.report.engine.ir.TableItemDesign.accept(Tab leItemDesign.java:69)
>> at
>> org.eclipse.birt.report.engine.executor.ReportExecutor.execu te(ReportExecutor.java:125)
>> at
>> org.eclipse.birt.report.engine.executor.ReportExecutor.execu te(ReportExecutor.java:89)
>> at
>> org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run (RunAndRenderTask.java:175)
>> at ExecuteReport.executeReport(ExecuteReport.java:84)
>> at ExecuteReport.main(ExecuteReport.java:100)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:324)
>> at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.ja va:202)
>> at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJav a.java:134)
>> at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
>> at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178 )
>> at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:275)
>> at org.apache.tools.ant.Task.perform(Task.java:364)
>> at org.apache.tools.ant.Target.execute(Target.java:341)
>> at org.apache.tools.ant.Target.performTasks(Target.java:369)
>> at org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1216)
>> at org.apache.tools.ant.Project.executeTarget(Project.java:1185 )
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:40)
>> at org.apache.tools.ant.Project.executeTargets(Project.java:106 8)
>> at org.apache.tools.ant.Main.runBuild(Main.java:668)
>> at org.apache.tools.ant.Main.startAnt(Main.java:187)
>> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
>> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
>> 10 avr. 2006 10:16:50
>> org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
>> INFO: memoryCacheRowCount is 20000
>> 10 avr. 2006 10:16:51
>> org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
>> INFO: MemoryCache is used
>> 10 avr. 2006 10:16:51
>> org.eclipse.birt.data.engine.executor.cache.SmartCache populateData
>> INFO: Time consumed by cache is: 1 second
>>
>> regards,
>>
>> Ludo
>>
>> Marc Leineweber a écrit :
>>> Hi again,
>>>
>>> the behavior I described (everything OK when no special character was in
>>> the text) was shown for a small xml data source and with only one data
>>> set defined. Now, with a more complex report and for that a bigger xml
>>> file, I have the problem as you described it - even without any special
>>> character... Did you find a solution yet? I would appreciate any hint.
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>> "Marc Leineweber" <marc.leineweber@icc-gmbh.de> schrieb im Newsbeitrag
>>> news:e1ii92$41n$1@utils.eclipse.org...
>>>> Hi Ludo,
>>>>
>>>> I have a similar problem, the reason in my case is an & character in my
>>>> text (I use an XML data source, BIRT 2.0.1) - that character and the end
>>>> of the text of the field after that character are truncated. Even the
>>>> &amp; entity does not work. Does your text contain an & and if yes, did
>>>> you find a workaround or solution to display this character?
>>>>
>>>> Or does anybody else have seen this problem and may provide a solution?
>>>>
>>>> Regards,
>>>>
>>>> Marc
>>>>
>>>>
>>>> "Ludovic CWI" <ludovic.chane-won-in@atosorigin.com> schrieb im
>>>> Newsbeitrag news:e1d594$eq1$1@utils.eclipse.org...
>>>>> Hi all,
>>>>> I have a problem when I render my birt report. Some data of my dataSet
>>>>> is truncated !!!
>>>>> My report consists in an xml data source and a simple dataSet. The
>>>>> dataSet matches an xpath and collect some text. Those texts are more or
>>>>> less long and after n rows (dataRows), the text of the n+1 dataRow is
>>>>> truncated. Then, the following rows are okay but p rows after, my text
>>>>> is truncated and ... etc
>>>>> It seems to be a problem of cache memory. This problem appears not only
>>>>> on the report but already in the previsualisation of the dataSet in
>>>>> eclipse. Maybe, some dataSet parameters exist but I didn't find them.
>>>>> The only relevant parameters I found were cachedMetaData and
>>>>> cachedRowCount. I don't know how to use the cachedMetaData parameter
>>>>> and the cachedRowCount parameter can't resolve my problem.
>>>>>
>>>>> I'm lost, please help me ... and forgive me for my poor english
>>>>> Regards,
>>>>>
>>>>> Ludo
>>>>>
>>>>>
>>>>> ps : i can join the complete log if you need it
>
Previous Topic:Page Break Problem
Next Topic:OLAP
Goto Forum:
  


Current Time: Thu Jul 17 03:46:51 EDT 2025

Powered by FUDForum. Page generated in 0.31404 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top