Hibernate gives (way) more headache because of very unclear error messages.
Hibernate does a lot of checking (therefore more unclear error messages) and
safes programmers for mistakes more than OJB. Hibernate is session based
wich means that your object tree has boundaries outside the session scope.
The biggest and most occuring exception is therefore the lazy loading
exception. EG fetch a record store it in the http session and in the next
http request you cannot work with the record because the hibernate session
is closed, you will always have to refresh the record manually. With ojb you
dont need to refresh those objects. Some say that is bad because of the risk
of outdated data, but i think it is ok when you know how to handle this. The
hibernate criteria API is a monster, it is like the java Calendar API, dont
get me started;-). With OJB you can add criteria (AND & OR) to another
criteria. With hibernate you can only add "AND" conditions to a criteria,
you cannot add other criteria to criteria. In that case you have to fall
back to HQL, wich is just compact sql, wich we all trying to keep out of our
code. OJB is just simpler and a pleasure to work with, with hibernate you
are up for a fight, every day again.
When you know what you are doing i'd say go OJB, when you are not that sure
about yourself go hibernate, it is harder but safer.
rg,
Dennis
2006/4/18, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
>
> Hi ,
> I am begining to study o/r mapping as database layer for j2ee application
> ;
> so i decide to select between hibernate and ojb . Would you like to give
> me
> some information to make my decision
>
> thank in advanced,
> Regards ,
>
> --
> View this message in context:
> http://www.nabble.com/ojb-start--t1467235.html#a3965408
> Sent from the Apache DB - ObjectRelationalBridge Users forum at Nabble.com
> .
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
mvg,
Dennis
