Refer to Ed Roman's book, Mastering Enterprise Java Beans for guidance.
Generally, the facade design pattern presented by Gamma et al. in Design
Patterns: Elements of Reusable Object-Oriented Software should be followed
for the session beans; that is, the session beans expose facades to the
clients.  To learn how to best construct the facades to provide for
scalability, refer to Transactional COM+ by Tim Ewald.  While it is written
for developers of COM+ systems, it is, nonetheless, a superb text on the
architecture of component-based systems (and since J2EE followed the
MTS/COM/DCOM precursor to COM+ in all respects except for some features of
J2EE that are best avoided, its not difficult to apply Ewald's lessons to
J2EE systems.


-Craig McMurtry
 Toronto, Canada




                    Prashant Gaikwad
                    <P.Gaikwad@ZENSAR        To:     [EMAIL PROTECTED]
                    .COM>                    cc:
                    Sent by: A               Subject:     What must be a class Design 
Hierarchy..
                    mailing list for
                    Enterprise
                    JavaBeans
                    development
                    <EJB-INTEREST@JAV
                    A.SUN.COM>


                    06/07/2001 06:39
                    AM
                    Please respond to
                    Prashant Gaikwad






Dear all,
        I'm a system analyst and designer worked  on Oracle based
technologies for a while now but recently I've entered in J2EE/oject
technologies.

Problem is we have analyzed a system and have come up with number of
business use cases. We have to start the low level design phase now to
provide an Enterprise Wide solution . We have our EJB architecture model
ready. Now we have to transform  business requirements captured in the use
cases  into class diagrams and followed by other UML diagrams, that will
make up session beans and the entity beans ultimately.
Question is :-
What are the object oriented design techniques generally followed to design
classes and establish relationships among them. How do I organize my
session
bean classes and entity bean classes and using what OO
method/principles/technique. Basically its a very big system and I want to
follow standard OO design approach so that OO benefits cam be utilized.

All the OO design experts uer thoughts and suggestions will be greatly
appreciated.

cheers
Prashant







===========================================================================
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".



----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.

===========================================================================
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".

Reply via email to