EJB vs POJO/JDBC

I have 10 years of java programming experience. I have looked at Hibernate, EJB 2.1 Entity EJB and now EJB 3.0 where Entity EJBs are gone. I have a hard time convincing myself that EJB or object/relational mapping are any good for my purposes. Why could I not just stick to what I already know, Servlets, plain old java objects (POJO) and JDBC, code my SQL-statements or call a stored procedure.

So, I would like to here some comments from you. Do you really save that much time and coding effort on using object/relational mapping like Hibernate or Entity EJBs?

[576 byte] By [Mattias_32a] at [2007-10-3 5:52:15]
# 1

Depends.

EJBs are pretty good in distributed, highly transactional environments.

Hibernate is useful if you have large object models, plus other things to consider like lazy loading, caching...

These technologies are basically aimed at removing some of the burden of development in cases like the above ones.

But if you don't feel any burden on your shoulders, then they probably add no value...

karma-9a at 2007-7-15 0:00:54 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2
Could you give me a real world example of a system using CMP EJB?
Mattias_32a at 2007-7-15 0:00:54 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 3
Most financial institutions (e.g banks) I worked in.
karma-9a at 2007-7-15 0:00:54 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...