Javascript Error testing report using BIRT Viewer 3.7 [message #752762] |
Wed, 26 October 2011 10:07  |
Eclipse User |
|
|
|
I've created my rptdesign in Eclipse Indigo with Birt 3.7 and Tomcat 7. I have 7 class files that I've exported into a jar. To test, I created a Dynamic Web Project in Eclipse, dropped the jar in the WEB-INF/lib directory, and placed my rptdesign under the Webcontent folder. This method works fine.
My teammate has concerns that my jar is not portable. Next I try testing it outside of Eclipse using Birth Viewer 3.7. I drop the same jar under the WEB-INF/lib directory, and put the rptdesign in the project root, ie. ${tomcat installation dir}/webapps/BIRT/report.rptdesign. For some reason, I get a javascript error: init is not defined on the rptdesign.
Anyone know the issue here?
Thank you for your time and consideration,
Paula
|
|
|
|
|
|
|
|
|
|
|
Re: Javascript Error testing report using BIRT Viewer 3.7 [message #755256 is a reply to message #754629] |
Mon, 07 November 2011 14:55  |
Eclipse User |
|
|
|
What JavaScript do you have in the report?
Jason
On 11/3/2011 12:28 PM, paula.mcdowell wrote:
> Yes, Jason. This appears to be my issue with regards to the hanging
> threads. Thank you. I review this more in depth.
>
> Also, I just created a new test environment. This environment will be
> used to verify our reports before installing for client acceptance
> testing. I again, get the javascript error that is the original subject
> of this ticket. The rptdesign file tests fine in my local environment
> after I recreated it as detailed in this ticket. Once I move it to the
> new environment, the browser error console displays a javascript error
> "init is not defined". This concerns me of course. I don't want to have
> resolve this same issue every time I migrate up to the next environment.
>
> I have simple javascript in my rptdesign. I believe this is causing the
> initial heartburn when I migrate to a new environment. When I remove the
> javascript, the report displays fine. When I re-add the javascript, the
> report still works. It appears to only have an issue with the javascript
> upon initial installation to the new environment.
>
> Does anyone know of any known issues? Or even better a resolution to fix
> other than removing the javascript permanently?
>
> Thank you for your time,
> Paula
|
|
|
Powered by
FUDForum. Page generated in 0.52238 seconds