Jaxor still funcitons with the mindset of mapping table -> objects and querying the mappings. IBatis maps SQL to objects not Tables to Objects. Also, i am very suspect of their sql support. I'm not certain it is true SQL. It looks as though it may use SQL constructs yet it is not the actual sql that reaches your database. I may be wrong. Also, jaxor does not abstract it's sql from the java class. It only abstracts the mapping to entity objects from the java class.
That's just a quick overview of what i saw. I'd be interested to hear what others have to say. Brandon On Thu, 17 Mar 2005 13:19:22 -0500, Jason Hall <[EMAIL PROTECTED]> wrote: > > > Hi, > > I was just reading up on Jaxor, similar to ibatis using a xml mapping > technique and traditional SQL queries. > But it provides more, like "unit of work", identity, etc. It seems > intrieging. What's significantly better in ibatis than Jaxor? > > > Thanks:) > > Jason Hall
