The best Java ORM

thanks...

is the new java 6 worth anything in this respect. I saw you could do
stuff using annotations, but im unsure how it deals with aggegating
various tables etc....

thanks for all the suggestions... I'll definetily have a look at them.
Which ones do you have experience with?


alexr wrote:
> carlo wrote:
> > Hello. I am in the need for a good ORM layer. I have a huge application
> > in which sql is all over the place and is distributed amongst many
> > computers. Thus my requirements are
> >
> > - sql must explicit but managed. Hibernate/JDO automating everything is
> > not an option.
> >
> > - free/cheap but still actively supported
> >
> > - for java
> >
> > I have been looking at Mr. Persister, but it seems to simplistic. I am
> > about to evaluate SimpleORM, but it seems not to be developed anymore.
> >
> > HEEELP
>
> Hi Carlo,
>
> There are a couple of options out there that I think might fit your
> description
> 1. iBatis http://ibatis.apache.org
> SQL is managed in configuration files.The framework maps a row
> from a result set to an object, or an object to a prepared statement.
>
> 2. SQLC
> http://www.hammurapi.biz/hammurapi-biz/ef/xmenu/products/common/index.html#SQLC
> The framework will generate java library for a set of SQL
> statements specifiied in configuration file. The project will then use
> the generated library.
>
> 3. JDBCPersistence. http://www.jdbcpersistence.org
>
> The framework will map rows from a result set to a set of java
> beans, or an object to a prepared statement. next release will include
> batched updates and partial objects, due in 2 month.
>
> Hope this helps
 >> Stay informed about: The best Java ORM 

carlo wrote:
> thanks...
>
> is the new java 6 worth anything in this respect. I saw you could do
> stuff using annotations, but im unsure how it deals with aggegating
> various tables etc....
>
> thanks for all the suggestions... I'll definetily have a look at them.
> Which ones do you have experience with?
In my opinion current persistence options are quite complicated, partly
due to the desire to adhere to complex APIs such as JPA which is based
on annotation, partly to the desire to provide support for all of the
possibilities. My experience had shown to me that a library that makes
simple things simple while complex things possible will always provide
better value then a complex library which makes all things complex.
Most of the libraries introduce SQL like proprieatary language that
makes things ever more complicated.

I had experience with iBatis as an evaluator, with Hibernate as a
library user. http://www.JDBCPersistence.org is the library I developed
to meet my requirements of simplicity and performance.

Good luck in your choice.
 >> Stay informed about: The best Java ORM