Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316468 - Cannot open the connection for the driver - Oracle
Summary: Cannot open the connection for the driver - Oracle
Status: CLOSED DUPLICATE of bug 305757
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.5.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 2.6.0   Edit
Assignee: Birt-Data-inbox@eclipse.org CLA
QA Contact:
URL: http://www.eclipse.org/forums/index.p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 10:15 EDT by Stefano CLA
Modified: 2010-06-11 13:10 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefano CLA 2010-06-10 10:15:29 EDT
Build Identifier:  v20100210-0630

I create a report that use data from a database Oracle via jdbc driver (classes12.jar).

If I run report in Eclipse Report Design view throw Firefox it work well.

Now I tried to run it in Birt Viewer application deployed in JBoss AS 5.1
Birt Viewer work well as I see the test page.

But when I run on Birt Viewer a report that use a jdbc to connect to a database it display this exception: Cannot open the connection for the driver: org.eclipse.birt.report.data.oda.jdbc.dbprofile.

I also add jdbc driver in Birt Viewer folderdeploy/birt.war/WEB-INF/platform/plugins/org.eclipse.b irt.report.data.oda.jdbc_2.5.2.v20100205

How can I resolve the problem ?

Reproducible: Always
Comment 1 Linda Chan CLA 2010-06-10 21:54:02 EDT
There is not enough info to diagnose the issue, as it is not reproducible.
Can you try with the latest BIRT 2.6, where this problem should no longer exist.
Comment 2 Stefano CLA 2010-06-11 03:11:47 EDT
http://www.eclipse.org/forums/index.php?t=msg&th=167273&start=0&

Here there is a previuos discussion about the same problem.
Comment 3 Linda Chan CLA 2010-06-11 13:10:25 EDT

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