Is iBatis an API which allows me to persist my POJOs to a datasource? If so, do you think it's easier to handle than Entity Beans or Hibernate.
What about the DAO pattern, shall I write a iBatis DAO?
Regards,
Darya
If so, do you think it's easier to handle than Entity Beans or Hibernate.
Originally posted by Brandon Goodin:
... iBATIS is a tool to interact with a database via a Datasource. iBATIS uses JDBC to pass sql to the database and then translates the returned resultset into Java objects according to the parameters defined by the developer. iBATIS provides caching that can reduce needless hits against the database.
Originally posted by Clinton Begin:
... I'm a fan of either avoiding the DAO pattern or writing a custom abstraction layer for a project.
Cheers,
Clinton
Where in an J2EE environment does iBatis belongs? After your answer, I have the feeling that iBatis has no realtion to J2EE at all.
Isn't a DAO pattern a pattern that belongs to J2EE or at least is heavily used there?
Maybe a small example can share some light