If you have this scenario: A is associated with C. B is associated with D. B extends A. A, B, C and D are Entity Beans. A and B use the JOINED strategy for Inheritance.
What is the best way to represent this kind of scenario with Session Beans? I thought about these 3 possibilities: 1- 4 Session Beans: Asession extends Bsession, A has @EJB Csession and C has @EJB Dsession. 2- 4 Session Beans: Bsession has @EJB Asession, A has @EJB Csession and C has @EJB Dsession 3- 3 Session Beans: 2 beans for C and D, and one Session Bean for the hierarchy. What could be the best choice, if you also have in mind that A has other children and B too? What is the "standard" solution using a EJB3 approach? What solution gives the best implementation, is smarter than the other, and is not too heavy in the server side? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912870#3912870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912870 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
