Hello, I d'like to use iBatis for refactoring an old J2EE project that uses a mix of pure jdbc and hibernate+DTO for its database access layer. I feel that iBatis is the way to go because I just want to simplify JDBC, I don't want magic proxies that blow up anywhere in my application because they contain references to closed database connections or anything like this...
My problem is that I'm unsure which version I should use, stable 2.xx or beta 3. Their respective API seem rather different, I like the session approach of version 3, especially because it would allow for example to pass Session objects to methods B and C to make them part of a single database transaction started by A, it seems cleaner to me than having them accessing the same static SqlMapClient object, I also prefer unchecked exceptions. Of course v3 is beta, documentation might not be perfectly up to date, there's no user javadoc (or I could not find one) but if we're close to a release (are we?) I would prefer to start working directly with the new Ibatis API to avoid migrating code later. Do you think v3 is stable enough? Can we expect a RC or stable release soon (1-3 months)? Any advice? -- View this message in context: http://old.nabble.com/Should-I-use-Ibatis-2-or-3-for-a-new-project--tp26713439p26713439.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org
