Just a quick check on this (closed) issue. I'm not sure that I understand how this got resolved. As best I can tell, the fix is in the new typing system in trunk (2.4.x), but there was no specific fix for 2.3.x.
Since this affects 2.3.0, and I think it's a pretty significant bug (certainly bit me hard!), what's the call on my patch? There's logic already in the class to cover the 'new Long(1) != new Integer(1)' case, this just extends it to cover the BigInteger and Short cases. Should I re-open the JIRA issue, or is this one not that important? --saul > > In the mean time, do you think there's a clean way to resolve this issue > for the 2.3.x branch so that folks using the 1.5.x branch of geoserver > with ArcSDE can get working "java.lang.Short" filters without having to > patch geotools themselves? > > --saul ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
