apache jboss static rendering

Long time back i have thought about this idea. But only few days back i had the oppurtunity to implement. With help of mod-jk, we are albe to comfirtably setup the worker processes. For this apache behaves as the primary webserver to which the request is pointed to. I have seen in many cases where static htmls are still devlivered or handled by the application servers like jboss working behind. It’s just a hit/miss story. So why dont we just have the static html in the apache server and deliver it to the client.

There have been questions on this subject/setup of delivering pages to clients. Since the maintanance is a bit difficult and the software buldling does not entertain this way of setup generally. But i always feel that it’s not fair to allow application servers to server the html’s. One another concern opposing my point could be the authentication or security handles by the applications. But that can be easily avoided by having dynamic rendering and auth in the app and once the auth stuffs are over, it’s just the hits at the webserver. I feel this methodology is more efficient provided we have good engineering of the bundling process.