I am in the process of designing a new application based on Seam and EJB3 and I want to get some design help/best practices since it has been a while since I developed a web-based app. My application will be accessed by the web-tier and through other mechanisms (possibly RMI or webservices). So, I was wondering what is the best approach to my design. Traditionally, I would probably design my business tier and provide light-weight facades for each other tier to access those business objects. Does this apply here? Based on the examples that I have seen (and I haven't been through all of them), the beans being used by seem have web/display knowledge incorporated (like the @DataModel and @DataModelSelection). To me, this wouldn't really play well if I was accessing the data through something like RMI. So, I guess my question is: Should I design my app to have my business logic in stateful/stateless beans (based off of the seam paradigm) and then have the web-based access layer (ie. the seam actions paradigm) in separate beans that manage the creation/selection/etc.. of the display based knowledge. If not, can someone give me some pointers. I am trying to quickly get an application off the ground and I don't want to make a lot of "newbie" design mistakes that I have to redesign/fix in a few months. Your expertise in this area would be greatly appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983546#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...