| Problems with 2.0 [message #117339] |
Thu, 26 January 2006 11:53  |
Eclipse User |
|
|
|
Originally posted by: jake.westviewclose.co.uk
Hi,
I'm just wondering if anyone else is suffering the same problems as me?
I've just migrated my "test" machine to use 2.0 Final. I've copied over
the 12 reports I've written so far in 1.0.1 and tried to run the
reports. I've already found three "problems" and i've only run one
report so far.
1) Time / date formatting is wrong.
I have a display field like so:-
row["course"] + " " + row["time"]
this show me in BIRT 1.0.1
Cheltenham 13:30:00
in 2.0 the date formatting has gone awry.
If I use row["time"] on its own and format it as hh:mm:ss I get 13:30:00
If i put another field in (add row["course"] - the formatting is
completely lost and it shows
Cheltenham Thu Jan 01 1970 13:30:00 GMT -0000 (GMT)
I can't seem to stop this from happening.
2) Page breaks are no longer working.
I've got a page break that is the footer of the "controlling" table. But
it doesn't generate a page break?
3) Most seriously, the very first report i run will not complete. Its
about 20 pages long. If i cut it down to 8 pages it will run ok. But if
I try to run for 9 pages (this can be controlled through a dataset), the
report completes but gives the error message
"The file is damaged and could not be repaired"
This is the same error message that FOP generated when it blew the
available memory. However FOP was incredibly memory intensive, but did
manage to run for around 40 pages before it blew.....IText(if that is
the problem is managing 8 pages?)
Can anyone let me know if these are "known" bugs? Or if i should report
them?
Its a bit worrying as this is probably the "simplest" of the 12 reports
i've written and this means that there is no way that I can move to BIRT
2.0. (Another worry is that the PDF generation seems far slower using
IText?) - has anyone noticed this that has migrated to 2.0 successfully?
Apologies for the length of the email, just trying to keep everything in
one place.
Jake
|
|
|
| Re: Problems with 2.0 [message #117723 is a reply to message #117339] |
Thu, 26 January 2006 17:50  |
 Stanley Wang
Messages: 81
Registered: July 2009 |
Member |
|
|
Jake Day wrote:
> Hi,
>
> I'm just wondering if anyone else is suffering the same problems as me?
>
> I've just migrated my "test" machine to use 2.0 Final. I've copied over
> the 12 reports I've written so far in 1.0.1 and tried to run the
> reports. I've already found three "problems" and i've only run one
> report so far.
>
> 1) Time / date formatting is wrong.
>
> I have a display field like so:-
>
> row["course"] + " " + row["time"]
>
> this show me in BIRT 1.0.1
>
> Cheltenham 13:30:00
>
> in 2.0 the date formatting has gone awry.
>
> If I use row["time"] on its own and format it as hh:mm:ss I get 13:30:00
>
> If i put another field in (add row["course"] - the formatting is
> completely lost and it shows
>
> Cheltenham Thu Jan 01 1970 13:30:00 GMT -0000 (GMT)
>
> I can't seem to stop this from happening.
>
>
> 2) Page breaks are no longer working.
>
> I've got a page break that is the footer of the "controlling" table. But
> it doesn't generate a page break?
>
> 3) Most seriously, the very first report i run will not complete. Its
> about 20 pages long. If i cut it down to 8 pages it will run ok. But if
> I try to run for 9 pages (this can be controlled through a dataset), the
> report completes but gives the error message
>
> "The file is damaged and could not be repaired"
>
> This is the same error message that FOP generated when it blew the
> available memory. However FOP was incredibly memory intensive, but did
> manage to run for around 40 pages before it blew.....IText(if that is
> the problem is managing 8 pages?)
>
>
> Can anyone let me know if these are "known" bugs? Or if i should report
> them?
>
> Its a bit worrying as this is probably the "simplest" of the 12 reports
> i've written and this means that there is no way that I can move to BIRT
> 2.0. (Another worry is that the PDF generation seems far slower using
> IText?) - has anyone noticed this that has migrated to 2.0 successfully?
>
> Apologies for the length of the email, just trying to keep everything in
> one place.
>
> Jake
I am not quite clear with the second case, i.e., what is a "Controlling"
table?
The third case is probably related to the specific report, as we have
tested much longer reports.
Please log bugs for all three cases, preferrably with reports that use
data from sample DB, or other sources that we can reproduce.
Stanley Wang
BIRT Engine
|
|
|
| Re: Problems with 2.0 [message #118092 is a reply to message #117339] |
Thu, 26 January 2006 21:06 |
Gary Xue
Messages: 193
Registered: July 2009 |
Senior Member |
|
|
Jake,
I can answer your first question. The change in display for expression like
( row["course"] + " " + row["time"] ) is the result of a bug fix. Since BIRT
expressions are defined to be Javascript expressions, when you put an
expression like ( string_value + datetime_value) in a data cell, two things
will happen:
(1) datetime_value is converted to a String as per Javascript rules. The
resulting string is in a long format which is probably not what you want.
(2) the entire expression returns a String. So as far as BIRT engine is
concerned, the expression is a String expression, and you cannot apply
date/time formatting rules on it.
For these reasons, I would discourage the use of string concatenation
operator "+" in your script expressions. You'll be much better off putting
the two different columns in two adjacent data elements, so that you can
apply different formatting rules on them.
If you must use string concatenation, you will need to do your own
formatting, like this:
t = row["time"]; row["course"] + " " + t.getHours() + ":" +
t.getMinutes()
Check the Javascript (ECMAScript) spec to see what other functions you can
use on its native Date class.
regards,
--
Gary Xue
Actuate Corporation - Product Development
BIRT Committer
"Jake Day" <jake@westviewclose.co.uk> wrote in message
news:drad81$3vq$1@utils.eclipse.org...
> Hi,
>
> I'm just wondering if anyone else is suffering the same problems as me?
>
> I've just migrated my "test" machine to use 2.0 Final. I've copied over
> the 12 reports I've written so far in 1.0.1 and tried to run the
> reports. I've already found three "problems" and i've only run one
> report so far.
>
> 1) Time / date formatting is wrong.
>
> I have a display field like so:-
>
> row["course"] + " " + row["time"]
>
> this show me in BIRT 1.0.1
>
> Cheltenham 13:30:00
>
> in 2.0 the date formatting has gone awry.
>
> If I use row["time"] on its own and format it as hh:mm:ss I get 13:30:00
>
> If i put another field in (add row["course"] - the formatting is
> completely lost and it shows
>
> Cheltenham Thu Jan 01 1970 13:30:00 GMT -0000 (GMT)
>
> I can't seem to stop this from happening.
>
>
> 2) Page breaks are no longer working.
>
> I've got a page break that is the footer of the "controlling" table. But
> it doesn't generate a page break?
>
> 3) Most seriously, the very first report i run will not complete. Its
> about 20 pages long. If i cut it down to 8 pages it will run ok. But if
> I try to run for 9 pages (this can be controlled through a dataset), the
> report completes but gives the error message
>
> "The file is damaged and could not be repaired"
>
> This is the same error message that FOP generated when it blew the
> available memory. However FOP was incredibly memory intensive, but did
> manage to run for around 40 pages before it blew.....IText(if that is
> the problem is managing 8 pages?)
>
>
> Can anyone let me know if these are "known" bugs? Or if i should report
> them?
>
> Its a bit worrying as this is probably the "simplest" of the 12 reports
> i've written and this means that there is no way that I can move to BIRT
> 2.0. (Another worry is that the PDF generation seems far slower using
> IText?) - has anyone noticed this that has migrated to 2.0 successfully?
>
> Apologies for the length of the email, just trying to keep everything in
> one place.
>
> Jake
|
|
|
| Re: Problems with 2.0 [message #118154 is a reply to message #118092] |
Thu, 26 January 2006 22:23 |
| Eclipse User |
|
|
|
Originally posted by: jake.westviewclose.co.uk
Gary,
Thanks for your help in this. Most appreciated. I've been "working" on
getting my existing reports to generate in 2.0 for most of the day, with
i'll admit limited success..... but at least this chalks off one of the
problems I had.
Thanks again
Jake
Gary Xue wrote:
> Jake,
> I can answer your first question. The change in display for expression like
> ( row["course"] + " " + row["time"] ) is the result of a bug fix. Since BIRT
> expressions are defined to be Javascript expressions, when you put an
> expression like ( string_value + datetime_value) in a data cell, two things
> will happen:
> (1) datetime_value is converted to a String as per Javascript rules. The
> resulting string is in a long format which is probably not what you want.
> (2) the entire expression returns a String. So as far as BIRT engine is
> concerned, the expression is a String expression, and you cannot apply
> date/time formatting rules on it.
>
> For these reasons, I would discourage the use of string concatenation
> operator "+" in your script expressions. You'll be much better off putting
> the two different columns in two adjacent data elements, so that you can
> apply different formatting rules on them.
>
> If you must use string concatenation, you will need to do your own
> formatting, like this:
> t = row["time"]; row["course"] + " " + t.getHours() + ":" +
> t.getMinutes()
>
> Check the Javascript (ECMAScript) spec to see what other functions you can
> use on its native Date class.
>
> regards,
|
|
|
|
| Re: Problems with 2.0 [message #122582 is a reply to message #117339] |
Wed, 01 February 2006 12:34 |
| Eclipse User |
|
|
|
Originally posted by: r.budner.abg.com.pl
Hi.
There is another solution for your first problem.
Use "Text" instead of "Data". Then choose "HTML/Dynamic Text" option.
You will be able to write code like this:
bla bla bla <value-of>row["course"]</value-of> <value-of format="dd MMMM
yyyy">row["time"]</value-of>
of course you will have to apply your own date format.
This is the way you can concatenate two date fields with different
formatting.
Greetings,
Robbo
|
|
|
Powered by
FUDForum. Page generated in 0.03194 seconds
] 
Search
Help
Register
Login
Home
