Hi all architects in this forum in all Seam examples you can see that the idea of Seam is to code JSP specific information like the next page ("/registered.jsp") in the Session Bean on the EJB container. Doing so the EJB level is aware of the upper level, Web in this case. Wouldn't it be better to stay neutral and enable Rich-Client (Swing or any Standalone Java-Client) to use the same Stateless Bean? Originally, the idea of EJB was to allow at least these 2 clients (Web-Container and Java-Client). Or is the Seam idea to duplicate Session Beans, one for web container and another for Java-Client? What is you opinion? Thanks for a feedback. Alain Hsiung View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037522#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...