Originally posted by Peter Lee: What is the drawback of using OR tools instead of CMP?
Beats me. An O/R persistent class can't act as a distributed component the way an entity bean can, but given that it's best practice to access entity beans only through a session facade anyway, that's hardly a drawback. Many OR tools can distribute with the best of them, if that's your thing, with distributed transactional caches and so on.
Is OR tools really save a lot of programming works compared with EJB? Do you think it is a trend to use OR tools for persistence?
Yes, and yes. A transparent O/R mapper means not only less programming effort, it also means an easier programming model, support for object orientation, in many cases dispensing with value structs^H^H^H^H^H value objects (aka data transfer objects) and other ugly kludges^H^H^H^H^H J2EEpatterns such as Fast Lane Reader, and is much easier to test.
- Peter [ August 21, 2004: Message edited by: Peter den Haan ]