Question about Hibernate vs select query/EJB

Question

HI all
i just want to understand the benefit of using Hibernate to map table to java object. normally we use select sql to get data and populate objects with the result set for simple situation, and if it gets complicated, we may use Entity Beans for persistence. now we have this hibernate concept that maps a table to a object, and use the hibernate APIs or queries to populate data. what is the big difference. the hibernate claims to be ultra high performance, any thought? thanks for your help and insight.

Answer 1

I have to say I wonder whether EJBs are much use at all. I think we need to explicitly say entity beans here. I think SLSBs and MDBs are decent and will remain even if CMP entity beans fade.
The EJB model says have a container because it takes care of a lot of things for you (e.g., distributed, transactions, threading, clustering, lifecycle, etc.) For those apps that don't need those things, don't use EJBs.
They have the feeling of being one of those management-driven fads. I think it's more like Sun and the designers of EJB had an initial idea, EJB 1.0, that has turned out to be non-performant. EJB 2.0 tried to fix it with CMP. Still didn't work. We'll see if POJOs and ORM are the answer. Check back in five years. There's a lot to like, but I'm sure EJB 1.0 was the best effort by smart folks, too.
When you come down to it the
attraction seems to be the idea that you can use
weaker programmers (and I doubt the reality of that,
either).I don't think anybody ever said that. EJBs aren't trivial. The container relieves programmers from having to write their own transactions, threading, etc., but what's left is hardly "easy".
Certainly they've got to be extremely costly on
comupting and (more importantly) network power, and I
find it hard to believe they really simplify coding.I think the cost on computing and network power are just part of writing enterprise apps, which is where the E in EJB came from.
Lots of times the network problems come about because naive programmers do n+1 queries when n will do. Hibernate helps with that.
%