Hello Amit,
> What should be design strategy while designing an EJB application? What
> point of time should one decide on Entity/Session bean? Should one go for
> EJB identification after all the business objects have been identified OR
> the business objects should be identified,from the start itself,as entity
> or session? Should a application be heavily loaded with entity beans?
Keep the design as simple as possible. Use session beans as facades. Do not
to access entity beans from your client application. Go for use cases and
model them as session beans. Define the interfaces of your facade and the
you can think about the architecure behind. Use entity beans if you need
transactions, security, shared data and database abstraction.
We've established the 7-Rule: As an unexperienced designer you should not
have more than 7 enterprise beans in your project.
regards,
--
[EMAIL PROTECTED]
MATHEMA Software GmbH
N�gelsbachstra�e 25 b
91052 E r l a n g e n
D e u t s c h l a n d
Tel +49(0)9131/8903-0
Fax +49(0)9131/8903-55
http://www.mathema.de
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
