The Artima Developer Community
Sponsored Link

Legacy Design Forum
Composition Versus Inheritance

Advertisement

Advertisement

This page contains an archived post to the Design Forum (formerly called the Flexible Java Forum) made prior to February 25, 2002. If you wish to participate in discussions, please visit the new Artima Forums.

Message:

session entity bean

Posted by ajay jindal on October 17, 2001 at 4:49 PM

> > How to go about deciding whether to use session beans and entity bean?
> > How to distrubute the responsibilties?


> > How to go about deciding whether to use session beans and entity bean?
> > How to distrubute the responsibilties?

Answer : its a very descriptive topic in itself but in general while designing a system one must have to find out independent entities which are going to be persistant in database for longer than a client session i mean u may need them gaian ana again for example :: User, or Account, Product etc

Session beans are generally for putting the business logic which uses one or more entity bean and have side effact on the database.

better go through J2ee BluePrint available online to get detailed information ;;

Here is the URL

http://java.sun.com/j2ee/blueprints/earlyaccess.html

Hope it will be useful
:)

Ajay





Replies:

Sponsored Links



Google
  Web Artima.com   
Copyright © 1996-2009 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us