Same problem here using BIRT 2. OracleDriver Sep 15, 9: Linda Report message to a moderator. Is there any actual problem observed with the report output, other than seeing the log message? Hi, I am also getting a similar message org.
|Date Added:||16 June 2009|
|File Size:||47.41 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Source code: Class Statement.java part of org.eclipse.birt.runtime version 4.3.0
In my case there is no report output. Eclipse Community Forums Forum Search: When redeploying our reporting website with the BIRT 2. Sign up to our Newsletter A fresh new issue delivered monthly. Connection setO [ message is a reply to message ].
igjoring Mon, 21 September OracleDriver Sep 15, 9: Anette, Can you post the report you are getting this error for? Wed, 26 August Katerina Report message to a moderator. Thu, 10 September Iam getting similar info message: Loading JDBC driver class: Report message to a moderator.
The only error reported in the log is the one I posted above, “setSpecification is not supported”. The quoted message is not an indication of any error. Found JDBC driverinfo extension: Thu, 27 August Hi, I am also getting a similar message org. Tue, 05 January Jason Weathersby wrote on Tue, 15 September I receive “Can’t load the report query” errors for each query in the report and no results are returned.
The DB connection info is censored for security reasons. Guido, Can you post ingoring report?
Source code of the class Statement part of e version
I am thinking of upgrading from BIRT 2. I’ve encountered a similar issue trying to upgrade from 2. Trying to locate driver in drivers directory Sep 15, 9: Fri, 18 September Driver class not in class path: I entered bug today. Can you post the report?
I am also receiving this issue as well and am thw 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.
Tue, 15 September Thanks, Anette Report message to a moderator.
Mar 1, 4: This occurs with any report, even a newly created report with a simple query in it, so at least in my case a specific report isn’t needed to reproduce the error.