🚀 go-pugleaf

Went to a Java User's Group last week and the topic was EJB.  Here's a
10,000 foot view.

Use Entity Beans to represent the entities in your application. Entity beans
should contain all your INSERT, UPDATE, and DELETE SQL and they should use
Bean Managed Persistence and not Container Managed Persistence since CMP is
not "production-quality" yet.

Use stateless Session beans to model business processes that are performed
against the entities in the system. They can contain SELECT SQL but never
INSERT, UPDATE, or DELETE.  Stay away from stateful session beans as they
can degrade the scalability of your application.

- joe


"pnichols" <pwnichols@charter.net> wrote in message news:3b3d8029_2@dnews...
> Eli Barnett wrote:
>
> > I need a design example using ejbs. If I am develping a system should I
> > have the business model in session beans and database access in entity
> > beans or should I have the busness model in plain classes that
comunicate
> > with session beans and they do it with enity beans ?
> > Thanks for your help.
> > Eli Barnett
> > ebarnett@b4before.com
> >
> >
>
>
> Usually all business objects are Session beans in an EJB model.
>
> Unless you are doing some type of Fat client or JSP, I do not understand
> why you would want the business objects not implementing some type of
> Remote Interface. Since you are doing EJBs, I am assuming you want the
> business objects which will act on the entity beans to be scalable. Making
> any beans that are not remotable, would kill the scalable design (assuming
> you want to start with say three tiers and be able to graduate to more
> tiers as the need arises). But I do not have near enough info to suggest a
> model for what you are wishing to do. You migth want to go to the javasoft
> web site and look at the models presented there.
>
> Good luck.
>
>