It used to be that PoolMan worked with Castor 0.9.5,
JSDK 1.4, and a webapp I wrote (http://freshmeat.net/projects/ajaqs).
I've ported the webapp to Castor 0.9.7 and JSDK 1.5.
I now am trying to get PoolMan 2.0.4 to work with this configuration.
I consistently get a casting exception:
java.lang.ClassCastException: java.sql.Timestamp
at com.codestudio.sql.PoolManResultSet.getDate(PoolManResultSet.java:546)
...
when one of the webapp's JSPs tries to navigate through
a relational collection (that is lazy-loaded).
Well, I looked at the PoolMan code and it did look like there
were some problems with PoolManResultSet.getDate(), particularly
with how java.sql.Timestamp in some cases was not converted
to java.sql.Date.
I tried making some fixes to PoolMan and then re-compiling it
against JSDK 1.5, but that led to various porting issues I do not
(and perhaps cannot) tackle.
To sum up, can we now assume that PoolMan is obsolete
and cannot be configured with JSDK 1.5, Castor 0.9.7 -- in which
case, the online Castor documentation should reflect this limitation?
Or am I missing something?
Charles
Start your day with Yahoo! - make it your home page
