2004-01-19 14:46:10 UTC
There's quite a bit of similarity in terms of basic design and usage. Some of the main differences (advantages) of JingDAO are:
- Lifecycle and configuration support (via Pico or Avalon)
- No marker interfaces: DAO's do not need to extend com.ibatis.db.dao.Dao
- Custom URL Resolver support (ie- lookup DAO implementations via JNDI)
- Context values
- Supports inter-DAO dependencies (without requiring DAO's also use the DAO Manager)
I've used iBatis and had talked with Clinton about adding Avalon or Pico support. It's a great little framework and certainly a source of inspiration. It's also smaller -- less jar dependencies. Personally, the lack of marker interfaces and the lifecycle support is what really sets JingDAO apart.
Also, JingDAO is, in fact, its own all purpose IoC container (thanks to Pico and Avalon) while iBatis DAO Framework is really just a DAO Factory.
As for JingSQL, it was an interesting little project for me that I through together rather quickly. iBatis sqlmap is most likely better software, but I haven't used it too much.
