Right, I understand that you don't want to change your DAOs. I don't think you have to.
It sounds like you already have an EJB3 setup for DAO and business logic. Keep your EJB3 DAOs and simply use the @EJB in your Stateless Session Beans. At this point there is no Seam at all. Then feel free to mix Seam into your various controllers. This will keep Seam out of your DAOs while allowing you to take advantage of both frameworks within your service layer. You should be able to have exactly the architecture you diagram. The only caveat is that Seam1/Seam2 be implemented using EJBs. @EJB is an EJB3 annotation, not Seam. -Jim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928200#3928200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928200 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
