Bug 44007 - Data Validation could not be accomplished in POI 3.0
Summary: Data Validation could not be accomplished in POI 3.0
Status: RESOLVED FIXED
Alias: None
Product: POI
Classification: Unclassified
Component: HSSF (show other bugs)
Version: 3.0-FINAL
Hardware: All Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-03 00:44 UTC by Ragupathi P
Modified: 2007-12-03 06:17 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ragupathi P 2007-12-03 00:44:02 UTC
The data validation functionalities of Excel could not be accomplished in POI 
3.0. There is indeed a previous bug relating to this (Bugzilla # 27511). A fix 
is also been provided there. But the fix provided there works only with POI 
2.5.x. The additional class files provided there HSSFDataValidation, 
DVALRecord,  DVRecord) tries to call some methods in the base classes of this 
API, but unfortunately methods with the required signatures no longer exist in 
POI 3.0. Hence trying to compile these classes throws exceptions (shown below).

"DVRecord.java": org.apache.poi.hssf.record.DVRecord should be declared 
abstract; it does not define fillFields
(org.apache.poi.hssf.record.RecordInputStream) in 
org.apache.poi.hssf.record.Record at line 38, column 1
"DVRecord.java": cannot resolve symbol: constructor Record (short,short,byte[])
in class org.apache.poi.hssf.record.Record at line 137, column 9
"DVRecord.java": cannot resolve symbol: constructor Record (short,short,byte 
[],int)in class org.apache.poi.hssf.record.Record at line 150, column 9
"DVRecord.java": createPtg(org.apache.poi.hssf.record.RecordInputStream) in 
org.apache.poi.hssf.record.formula.Ptg cannot be applied to (byte[],int) at 
line 198, column 26

Is there way through which these Data Validation features could be implemented 
in POI 3.0?
Comment 1 Nick Burch 2007-12-03 06:17:17 UTC
Code now in trunk. 

Tests appear to pass, but it's always possible something got broken in porting
to the new style record code. Do let us know if you spot anything wrong with it :)