I read section 8.1.2 “Using Hibernate in a EJB container” with great interest. As far as EJB I am a newbie and am trying to get a grip on the whole philosophy.

I understand the working of the “EJB command pattern” and can see the obvious benefit of it as apposed to “Session façade” pattern.

My question is – why bother with the EJB container at all? Surely the servlet can perform functions like load sharing, fail safe tolerance and transaction coordination? What is the EJB actually giving you that cannot be performed with simpler methods?

Thanks for a great book!

Richard Schmidt

It's providing a standard programming model, runtime environment, and deployment options for these cross-cutting concerns. Servlets don't, its "do it yourself and see if it works".

I am looking for the source code for the CaveatEmptorFacade and CaveatEmptorFacadeBean but I am unable to find in the latest release of the CaveatEmptor package. Is it out somewhere or is what the book has all there is?

The ejb examples from chapter 8 are not in the latest code, I am trying to follow how it was configured and am unable to see it from the code in the book.

I am trying to set up an application using hibernate and the session facade ejb pattern. I am running Eclipse v3.1 m4 and myeclipse plugins. We have choosen the facade pattern because it will allow us to give access to the business layer to other applications in the enteprise, not all java. This may not be the best place to ask this question but I will give it a shot. I am having trouble determining the correct way of setting up the enviroment, should I set it up as a J2EE application and set up different projects for the EJB's, and web or do I just set it up as a web project and put the Session Facade ejb's in the package structure simmilar to the way it is set up in the caveat emptor example? Any feedback is greatly appriciated.
Tim

Please continue this discussion in the regular Hibernate User forum.