It's not that complicated:
- JBossWeb is targeted for users using standalone Tomcat that do not need EJB, and it can replace standard Apache Httpd+Tomcat for static content delivery, because it contains OPenSSL and APR native libraries for higher performance for the static content.
- Everything else is like before :)
I am glad that lightbulb asked this question! The answer may not be "complicated" for people who know. But I didn't find any answers until I saw this thread.
I use JBoss 4.0.4 and will soon migrate to 4.2.1. I spent quite a bit of time trying to figure out a way to get rid of Apache httpd altogether because of new architecture of JBossWeb. I can now stop this search because of the answer given in this thread.
I am curious, though, that if JBossWeb has comparable performance to Apache httpd because of APR, what are the reasons not to get rid of Apache altogether.
I'd appreciate any thoughts and/or references.