Hi,

I am trying to convince my existing employer to use Hibernate for our current project but the techincal architect is asking for some good reasons as to why he should choose Hibernate over EJB.

I have mentioned the advantages of going with Hibernate but I dont think he is convinced. Please help me out guys. If you could give me some solid reasons as to why he should choose Hibernate over EJB it would be very helpful for me. I personally think Hibernate would fit very well into this project. We dont even need EJB's in this project actually.



Thanks in advance for all your help!!! Waiting for your response ASAP

Cheers,
Ajit

The 2 aren't mutually exclusive.

Hi,

I know that they are not mutually exclusive but I dont want EJB to be used at all in the project since everything can be achieved using Hibernate alone.

What i am looking for is some solid points from which I can convince my technical lead to use Hibernate for the project and not use EJB at all.
I have put forward some points to him but he is still not convinced. Please help me Hibernate team. Only you guys can help me out here since you know your product best. Give me some USP's guys please.


Any help would be appreciated!!! Thanks in advance!!!

I don't get it. The Hibernate team are working very hard on the EJB3 spec. Why would we tell you to not use EJB?

Just because we don't like EJB 2.x *entity beans* doesn't mean EJB is all bad.

In fact, we think EJB 2.1 session beans + Hibernate3 is the closest approximation to what EJB 3.0 will look like when fully ready.

Hibernate with a service layer is a very powerful combination. You get the flexibility of hibernate object model with the JTA transactioning.

We've been using hibernate in this manner for almost 2 year now (has it really been that long?). However, for our current project we're moving towards a Command Pattern vs the Session Facade since it seems to fit a bit better.

Now, if your question is why Hibernate over Entity Beans then that's a completely different story. I would think that hibernate's features like Inheritance Mapping, Filters, Polymorphic Queries, etc, etc would give it a leg up.

Hey Guys,

Dont get me wrong here. Maybe I put the question the wrong way. I am not against EJB at all and I think the Hibernate team is doing a wonderful job working towards EJB 3.0 specification.

I want to use Hibernate as the service layer between the Database and the Business layer for persisiting objects . fetching , updating and other database operations. I am insisting that they use Hibernate for that simply because of all the features that it provides as an ORM tool.

But they want to use EJB as the middle layer and this is where I am trying to tell them that to plug in Hibernate since they are not mutually exclusive. So I am looking for some USP's that will make them understand the power and flexibility of Hibernate. Please help me out guys!!

The main problem is they dont understand why Hibernate is required when everything can be done using EJB's.

Thanks in advance!!! Any help is greatly appreciated

I have a serious question: why are you designing this system?

And: It will take you a long time to convince people of something they don't know about and which is a complex subject. Especially if you have to learn it first. I'd argue that you go with a design that worked for your team in the past if you don't have the time.

"power and flexibility" is not an argument, it can not be mesured and verified. Probably cost is the best argument, but it is not a developer business to calculate it.

Hi,

I have used Hibernate in the previous project and I am no expert in Hibernate but since I have experienced the advantages in using Hibernate I am insisting hard for using Hibernate in this project. But sadly I guess this time around its not going to happen :)

It is true it is hard to convince people but if you dont try then no one will ever be convinced.


Take care guys. Thanks for all your help!!!

Hey Guys,

Good news!!!!! I have finally convinced my team to use hibernate for our project. All i did was gave them a demonstration of all the features that comes with hibernate and they were impressed.

Great product guys!!!! Keep up the good work and once i told them that the EJB 3.0 uses the same exact api of hibernate for persistence they had no other arguments.

Gavin, Christian and team i must say you guys have created a wonderful ORM tool. I hope one day i can start contributing towards the project.


Thanks guys!!!
Cheers
Ajit