Hi Vinays,
One reason why I don�t personally like this architecture is because it might impact your application�s performances pretty badly. To be more precisely I�ll tell you that separating the web app and ejb container (and having separate war and ear) will make impossible for your
servlets or
jsp to access the ejbs via their local interfaces. Therefore every client call will result in at least one remote call form the presentation layer to the business layer. Therefore one needs to design the application using kind of command design
pattern strategy in order to reduce the number of calls from one layer to another. This will tide the application design to the system architecture as well.
On the other hand this architecture provides very strong security capabilities. Even more this is exactly the kind of requirements that advocate the need of using an ejb container. So I suppose the answer is somewhere in between: if all deployed applications were initially designed for this kind of hardware architecture, it might be an excellent solution. However it might not be the most optimal configuration for deploying all type of applications.
Regards.
