Bug 203101

Summary:

runtime WAR does not work in apache 5.5/jajav 1.5

Product:

z_Archived

Reporter:

Hari Nair <haridasan.t>

Component:

BIRT

Assignee:

Birt-ReportViewer <Birt-ReportViewer-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

normal

Priority:

CC:

cyfgod, haridasan.t

Version:

2.2.0

Keywords:

test

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
birt 2.2 runtime error / java 1.5 / apache 5.5.11/ windows xp	none

Description Hari Nair

2007-09-12 12:39:08 EDT

Build ID: v20070713-0630

Steps To Reproduce:
1.WAR FILE DEPLOYED UNDER APACHE 5.5.11/XP/JAVA 1.5
2.DISPLAYING ONLY THE FRAMESET (SHOWING ICONS) BUT NO REPORT
WHILE TESTING THE DEPLOYMENT WAR FILE INSTALLATION

UNABLE TO DEPLOY BIRT 2.2 REPORTS USING  BIRYT 2.2 WAR FILE - USED FOR DEPLOYMENT AS AVAILABLE FOR DOWNLOAD


More information:
DOWNLOAD BIRT 2.2 WAR FILE - RUNTIME
DEPLOY UNDER TOMCAT 5.5.11/XP/AVA 1.5
WHILE TESTING THE INSTALLATION, SHOWING ONLY THE FRAMESET AND NO REPORT

UNABLE TO DEPLOY BIRT 2.2 REPORTS

Comment 1 Jerry Cheng

2007-09-12 23:55:38 EDT

Can't reproduce this issue. Please check the latest build.

Comment 2 Hari Nair

2007-09-13 00:12:59 EDT

With the milestone version of BIRT 2.2 RUNTIME also the error exists
Unable to display reports.  The reports works fine in the BIRT 2.2 tool, But while deploying under timcat 5.5 /ajava 1.5 / windows xp,  report does not display data, only the frame is didplayed

Comment 3 Jerry Cheng

2007-09-13 01:07:14 EDT

Please check the log file in tomcat.

Comment 4 Hari Nair

2007-09-13 12:28:10 EDT

Created attachment 78337 [details]
birt 2.2 runtime error / java 1.5 / apache 5.5.11/ windows xp

BIRT 2.2 RUNTIME - LATEST BUILD 
REPORT NOT DISPLAYED
ONLY THE FRAME IS DISPLAYED .PL SE ATTACHMENT
WHILE RUNING THE TEST REPORT - RUNTIME 2.2

REPORT NOT GETTING DISPLAYED

ATTACHED IS ALSO APACHE LOG FILE
SE ALSO THE PICTURE ATTACHED

Comment 5 Jerry Cheng

2007-09-13 21:30:49 EDT

Currently, BIRT viewer doesn't support Opera browser.

*** This bug has been marked as a duplicate of bug 195478 ***