Responding back to the list... Sorry for the confusion.
I guess we should say that the DAO framework is "deprecated" in 2.2 and "removed" in 2.3. I believe that 2.2 will be declared GA any day now, so the DAO framework will be around for a while longer. But...If you are just starting with iBATIS, please don't use the DAO framework. Just use the SqlMap API directly, or use some other IoC container like PicoContainer or Spring. Your decision to use iBATIS was surely based on a lot more than the DAO framework - and all the great SqlMap functionality is still there. The DAO framework is a very small layer over iBATIS - very easy to duplicate in your own code if you need to. If you don't want to use Spring, then it's very simple to write your own DAOs just using the SqlMap API. Your only issue will be that the DAO framework provided a very elementary dependancy injection framework *for iBATIS objects only*. This is why it was deprecated - there are lots of better dependancy injection frameworks out there. I use Pico container in a lot of projects - very simple and does a lot more than the iBATIS DAO framework. Spring is even better - but has a slightly higher learning curve. But again, you don't have to use any of these things - iBATIS works perfectly fine using the SqlMap API directly. Jeff Butler On 12/4/06, Dave Rodenbaugh <[EMAIL PROTECTED]> wrote:
Hi Jeff, When you say "deprecated and removed" in the same sentence, that seems contradictory to me...Either it's deprecated (marked as going away, and still present in the codebase) or it's removed (and therefore, not deprecated)... This is sad news indeed. We just evaluated iBATIS and chose it because it did everything we wanted for a persistence framework. We are not Spring users, (nor EJB either) just using a persistence layer simplification for an existing enterprise app. By removing DAOs in 2.3, you're unfortunately limiting us to 2.2.x indefinitely. I hope that we made the right choice because it seems clear that support just dried up for 2.2. :( Please let me know which it is--deprecated or removed. Thanks, -Dave ------------------------------ *From:* Jeff Butler [mailto:[EMAIL PROTECTED] *Sent:* Friday, December 01, 2006 10:20 AM *To:* [email protected]; Ibatis Development List *Subject:* iBATIS for Java 2.3.0 Released! iBATIS for Java version 2.3.0 is now available. This release includes several bug fixes and enhancements. Additionally, this release offers new support for local caching of prepared statements. Caching prepared statements can lead to significant performance improvements in many environments. The Java DAO framework has been deprecated and removed from iBATIS as of release 2.3.0. We heartily recommend that you consider using the Spring Framework <http://www.springframework.org/> for all your DAO needs! Spring offers great support for iBATIS. The paginated list methods have been deprecated with this release. The methods were confusing to many users and often misused. We suggest using native database support for paging, or that you use the query methods with skip and max settings. Release 2.3.0 supercedes the 2.2.0 release which will remain at beta status due to minor bugs. We recommend that all 2.2.0 users upgrade to version 2.3.0. I expect that there will be a vote to promote 2.3.0 to General Availability status in two weeks. You can obtain the new release here: http://ibatis.apache.org/javadownloads.cgi Enjoy! Jeff Butler
