IGNORING THE UNSUPPORTEDOPERATIONEXCEPTION THROWN BY ODA DRIVER DOWNLOAD

Guido, Can you post the report? ReportAction] [filipski] Report parameters ready if any It's a sample report with no additional ODA data sources, just internal sample database. I am thinking of upgrading from BIRT 2. The reports seem to be ok, so I have no idea what is causing this Mon, 01 March However the generation of some graphs fail and the following error messages are logged in log of the application server JBoss AS 4. I entered bug today.

Uploader:	Kigarn
Date Added:	6 March 2011
File Size:	24.40 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	69805
Price:	Free* [*Free Regsitration Required]

Source code: Class Statement.java part of org.eclipse.birt.runtime version 4.3.0

Iam getting similar info message: The DB connection info is censored for security reasons. Tue, 15 September Anette, Can you post the report you are getting this error for? Loading JDBC driver class: Jason Anette Engel wrote: Can you open a bugzilla entry with this stacktrace?

Mon, 21 September Can you post the report? The only error reported in the log is the one I posted above, "setSpecification is not supported". ReportAction] thrkwn Report parameters unsupportedoperationexcepgion if any It's a sample report with no additional ODA data sources, just internal sample database.

When redeploying our reporting website with the BIRT 2. I've encountered a similar issue trying to upgrade from 2.

Source code of the class Statement part of e version

Mar 1, 4: Connection setO [ message ]. No named Parameter supported.

Jason Jason Estep wrote: Found JDBC driverinfo extension: Jason Guido Garcia wrote: Same problem here using BIRT 2. Tue, 05 January Eclipse Community Forums Forum Search: Guido, Can you post the report? Thu, 17 September However the generation of some graphs fail and the following error messages are logged in log of the application server JBoss AS 4. Linda Chan wrote on Fri, 18 September OracleDriver Sep 15, 9: The important part of the error appears to be these two lines: Mon, 01 March Thanks, Anette Report message to a moderator.

I am also receiving this issue as well and am now wondering if this could be the problem that is causing me too see what I orginally believed was a cached or out of date report. I am using BIRT 2. I entered bug today. I receive "Can't load the report query" errors for each query in the report and no results are returned. Linda Report message to a moderator.