Hi, I have a design issue. DESIGN : ---------- We can design a set of beans in 2 ways: (1) First, follow the aggregate entity pattern and make all the so called beans into java classes. Then have an aggregate relationship with all the Java Classes with one bean which satisfies the life-cycle of all these classes. ( For e.g. we can have Java Classes like : CUser,CAddress, CBankInfo, CContact etc. etc. which map to a corresponding table in the database and one bean called say USER which has an aggregation relationship with all of them.). In this case we need to go for BMP. (2) the 2nd way is to make all of these individual Java Classes into Beans and go for CMP. ISSUE: ---------- Which of the ways U think is better? And why? Actually, I liked the first way because there is no bean to bean communication. And every thing is done in one shot. PROBLEM: -------- Now say I choose to go by the first way and instead of having an aggregate relationship of the individual classes with the bean I choose to have an aggregate relationship amongst the classes ( i.e. btwn CAddress,CBankInfo etc something like a user (CUser) can have many addresses ( CAddress ) and at the same time have some bank info (CBankInfo) as well as a contact address ( CContact ). So, in CUser class we have as member variables as CAddress, CContact, CBankInfo, etc. Then, I decide to make this CUser a member variable of the USER Bean. ( So automatically every thing comes inside CUser ???? ). But, this design concept does not work. Or can it work ? I HOPE A LOT OF RESPONSE FOR THIS ISSUE. Thanks in advance :-) Rashid. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 =========================================================================== 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".
