Not to start a discussion on development and design rules... ...But if you start treating Session beans like DAO's, you end up with: A) Facade's with 10k line of code B) Session Facades calling Session DAO's (which is a total waste of resources since JNDI lookups, even internal ones, aren't exactly 'lightweight' operations)
You wouldn't want either of these options and I feel you are suggesting option B.... well..... 'JNDI lookup BAAAAAAD' must prevent it as much as possible. If an entire chain of objects must be turned into 'Session beans' simply to be able to use the entity manager, EJB3.0 would be in a world of hurt, because not a single Enterprise-sized application could be buildt with it then, since a basic operation can string between depths of 2-15 objects. You want to turn all of these into session beans? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947944#3947944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947944 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
