Since there's nothing in this relase so far that the community is really wanting/needing, I think it would be worthwhile to take a look at some of the other open issues before doing another release. Specifically:
1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a serious triage). 2. I think we should allow a <resultMap> with no <result> sub elements per this conversation (I ran into this issue myself recently in one of my projects): http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html 3. Someone should take a serious look at this potential issue with prepared statement caching - at least make the error message more helpful than "this is likely a bug": http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html 4. Lastly (my continuing prodding) - any new feature that is added should be documented in the PDF. iBATIS is in wide enough use that we need to be more serious about our documentation. I'm thinking specifically of prepared statement caching, multiple result sets, and Oracle cursor support. Each of these things have generated multiple questions on the user list. We can't say "RTFM" if we don't have any FM :) Also, the PDF should be updated to reflect the new packaging for 2.3. I will have time over the holiday weekend to work on some of these, so I propose waiting at least another week or two. I'm -1 until some of these other issues are resolved one way or another. Jeff Butler On 11/20/06, Clinton Begin <[EMAIL PROTECTED] > wrote:
Hi all, I'd like to release iBATIS 2.3 sometime this week. The changes listed for the release are as follows: o DEPRECATED All PaginatedList related features due to misuse, minimal applicability and inflexibility o DEPRECATED DAO Framework -- Removed from primary distribution, available as a separate download o Removed DAO framework from Subversion source tree (tagged before removal) o Changed deployment file naming convention, dropped "DBL" and lowercased all o Merged common and sqlmap jar files (no more DAO means there's no point in keeping commons separate) o Implemented transaction level PreparedStatement caching o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies Cheers, Clinton
