Eclipse Community Forums: BIRT » 2.0 M3 to 2.0.0 issues

Home » Archived » BIRT » 2.0 M3 to 2.0.0 issues

2.0 M3 to 2.0.0 issues [message #119038]

Fri, 27 January 2006 13:07

Eclipse User

I just migrated my RCP installation and my Report Engine deployment from
2.0 M3 to 2.0.0 and have encountered the following two issues:

1)BIRT_VIEWER_REPORT_ROOT is no longer using the value I supply.
In M3 I have this set to c:/appServer/myWebAppRoot/reports
When I try this in 2.0.0 it will only find reports that sit
in myWebAppRoot. I have also tried a relative path to /reports
but I get the same behavior.

2)Charts are not displaying. I have opened these charts in the 2.0.0
RCP and have been able to preview fine there, but when I invoke using
the ViewerServlet I just get a blank page. No errors are generated and
the page contains nothing at all, viewing source displays nothing as
well. My tabular reports are displaying correctly.

Anyone with similar issues or ideas?

thanks in advance.
Brian

Re: 2.0 M3 to 2.0.0 issues [message #119090 is a reply to message #119038]

Fri, 27 January 2006 14:22

Eclipse User

For 1) set same value to "BIRT_VIEWER_WORKING_FOLDER".

Re: 2.0 M3 to 2.0.0 issues [message #119118 is a reply to message #119090]

Fri, 27 January 2006 15:07

Eclipse User

Jun Zhai wrote:
> For 1) set same value to "BIRT_VIEWER_WORKING_FOLDER".

Excellent, thank you!

Not sure how I missed this change, is it documented somewhere? I have
been using the web.xml that is included in the Web Viewer
Example/WEB-INF directory for the parameter definitions, which obviously
needs updating as it still refers to BIRT_VIEWER_REPORT_ROOT

Re: 2.0 M3 to 2.0.0 issues [message #119131 is a reply to message #119118]

Fri, 27 January 2006 15:22

Eclipse User

Originally posted by: zhai.actuate.com

This is a bug. We need to make sure the packaged web.xml has right
parameter name too.

Re: 2.0 M3 to 2.0.0 issues [message #119287 is a reply to message #119038]

Fri, 27 January 2006 18:03

Eclipse User

For the chart issue, what browser and OS you are using? Does it support SVG,
if not, you can disable SVG in the chart wizard.

Wenfeng

"Brian Kallay" <brian.kallay@bricsnet.com> wrote in message
news:drdnhq$nrs$1@utils.eclipse.org...
> I just migrated my RCP installation and my Report Engine deployment from
> 2.0 M3 to 2.0.0 and have encountered the following two issues:
>
> 1)BIRT_VIEWER_REPORT_ROOT is no longer using the value I supply.
> In M3 I have this set to c:/appServer/myWebAppRoot/reports
> When I try this in 2.0.0 it will only find reports that sit
> in myWebAppRoot. I have also tried a relative path to /reports
> but I get the same behavior.
>
>
> 2)Charts are not displaying. I have opened these charts in the 2.0.0
> RCP and have been able to preview fine there, but when I invoke using
> the ViewerServlet I just get a blank page. No errors are generated and
> the page contains nothing at all, viewing source displays nothing as
> well. My tabular reports are displaying correctly.
>
> Anyone with similar issues or ideas?
>
> thanks in advance.
> Brian

Re: 2.0 M3 to 2.0.0 issues [message #120060 is a reply to message #119287]

Mon, 30 January 2006 11:45

Eclipse User

Thanks for the reply Wenfeng, I am using firefox 1.5. I did test by
changing the output format from svg to gif, jpeg and png but I get the
exact same behavior with each setting. It is also my understanding that
if a report set to svg is requested from a non-svg supported browser
the engine is smart enough to display using a different format, but I
may be wrong on that.

Brian

Wenfeng wrote:
> For the chart issue, what browser and OS you are using? Does it support SVG,
> if not, you can disable SVG in the chart wizard.
>
> Wenfeng
>
> "Brian Kallay" <brian.kallay@bricsnet.com> wrote in message
> news:drdnhq$nrs$1@utils.eclipse.org...
>
>>I just migrated my RCP installation and my Report Engine deployment from
>>2.0 M3 to 2.0.0 and have encountered the following two issues:
>>
>>1)BIRT_VIEWER_REPORT_ROOT is no longer using the value I supply.
>>In M3 I have this set to c:/appServer/myWebAppRoot/reports
>>When I try this in 2.0.0 it will only find reports that sit
>>in myWebAppRoot. I have also tried a relative path to /reports
>>but I get the same behavior.
>>
>>
>>2)Charts are not displaying. I have opened these charts in the 2.0.0
>>RCP and have been able to preview fine there, but when I invoke using
>>the ViewerServlet I just get a blank page. No errors are generated and
>>the page contains nothing at all, viewing source displays nothing as
>>well. My tabular reports are displaying correctly.
>>
>>Anyone with similar issues or ideas?
>>
>>thanks in advance.
>>Brian
>
>
>

Re: 2.0 M3 to 2.0.0 issues [message #121819 is a reply to message #119038]

Tue, 31 January 2006 12:36

Eclipse User

Thanks for the responses,

In regards to #2 (Charts not displaying) it appears to be some cruft
from 2.0 M3 left in the plugins dir causing the issue. I did a
completely clean install and was able to resolve the issue.

thanks again,
Brian

Brian Kallay wrote:
> I just migrated my RCP installation and my Report Engine deployment from
> 2.0 M3 to 2.0.0 and have encountered the following two issues:
>
> 1)BIRT_VIEWER_REPORT_ROOT is no longer using the value I supply.
> In M3 I have this set to c:/appServer/myWebAppRoot/reports
> When I try this in 2.0.0 it will only find reports that sit
> in myWebAppRoot. I have also tried a relative path to /reports
> but I get the same behavior.
>
>
> 2)Charts are not displaying. I have opened these charts in the 2.0.0
> RCP and have been able to preview fine there, but when I invoke using
> the ViewerServlet I just get a blank page. No errors are generated and
> the page contains nothing at all, viewing source displays nothing as
> well. My tabular reports are displaying correctly.
>
> Anyone with similar issues or ideas?
>
> thanks in advance.
> Brian

Previous Topic:	Trying to get the pooled db connection working
Next Topic:	Cross table support in BIRT 2.0

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 07:23:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter