I fell for that problem, too. IMHO the Seam docs should prominently include some advice on application structure/layering to avoid this.
That's also the only suggestions I can make: Restructure your application and introduce clean layering to avoid any circular or overly complex dependencies. (So I'm afraid I have to ask why you want A and B to have a circular dependency.) I think it's best to have a first layer that is accessed by JSF: Components for action handlers and data models. Action handlers can of course have data models or entity beans injected, but not other action handers. If needed add some lower layers that can for example handle persistence or business logic. But I'd very much like to hear opinions of more experienced Java EE/Seam developers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947699#3947699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947699 ------------------------------------------------------- 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
