Of your possible choices I definitely don't recommend using stateless session beans everywhere. You should use an appropriate mix of stateless and stateful if you take the EJB route.
If you don't take the EJB route, you have a choice between Seam POJOs or Spring POJOs. In a JSF-based architecture, there is a compelling reason to choose Seam components: the contextual state management model is simply a much better fit to JSF, and the next rev of Java EE will include this model (the Web Beans spec). So it comes down to session beans or not session beans. Your choice. Try out EJB3. If you like it, stick with it. If you don't, use plain Seam components. You can always change your mind later. Note that there are a couple of problems for which you really do need EJB in Seam: eg. REQUIRES_NEW transactions and message-driven beans. However, you can always mix and match. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057808#4057808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057808 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
