Well, I am not a Seam developer but my stance on these issues is this: anonymous wrote : - security: presentation layer is the only one that gets exposed to the internet and it take hackers more layer to crack. | Once the machine hosting the view is hacked your are usually lost anyway. You usually need some direct access between the view layer and the database (fast lane pattern, authentification ...). Once they can hijack a machine with a ddatabase connecetion everything is lost ... anonymous wrote : - scalability: easier to scale either/both presentation and business layer if they are separated. In 99% of all projects improving the code has a far more dramatic effect than simply scaling out a poorly designed and implemented project. So it is usually not necessary to distribute the layers over different machines. If it is it is usually possible to cut the application into different functional units that can be distributed over different machines. Even once these options show to be insufficient the costs of RMI make (IMHO) distributing view layer and business code over different machines hardly worthwhile. Simply scaling out the combined view/business layer is (IMHO) the simpler approach. anonymous wrote : - easier division of labor: presentation and business-logic developers only care about their components and they can become more skillful/specialized in their area. Ease of division of labour is an issue of good design which should take place before the actual implementation is happening. A good design can not and should not enforced by choosing a certain technology. Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081819#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...