Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335936

Summary:	Report parameters of data type 'date' are converted from java.sql.Date objects to java.util.Date object when used as drill-through parameter of chart
Product:	z_Archived	Reporter:	Ed Slocombe <ed.slocombe>
Component:	BIRT	Assignee:	Heng Li <liheeng>
Status:	CLOSED FIXED	QA Contact:	Xiaoying Gu <bluesoldier>
Severity:	normal
Priority:	P3	CC:	bluesoldier
Version:	2.6.0
Target Milestone:	3.7.0 M7
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Ed Slocombe

2011-02-01 04:05:45 EST

Build Identifier: 

The thread discussion which led to the creation of this bug can be found here:
http://www.birt-exchange.org/org/forum/index.php/topic/21427-birt-parameters-of-date-type-normally-javasqldate-but-sometimes-javautildate/page__p__72658__fromsearch__1&#entry72658

This issue only applies to drill-through links of charts (of chart sections, as far as I'm aware).

A report with a chart which as interactivity on a chart section, passing a date parameter as one of the drill-through parameters, seems to convert the date object from a java.sql.Date instance to a java.util.Date instance. This doesn't cause any issues in the report viewer or  BIRT Eclipse preview tab. It causes me problems since production code contained within a BIRT intergrated web application is now throwing ClassCastExceptions where my code always expects parameters of date type to be instances of java.sql.Date.

See forum post for full details. 

Reproducible: Always

Comment 1 Heng Li

2011-04-12 22:39:22 EDT

The cause is chart uses Calendar.getTime() to return a Date instance, the default Date instance is java.util.Date. Now fixed it, add a check and return original java.sql.Date in class CDateTime.