Chapter 5. Configuring JBoss Web Server
This chapter covers
- Configuring web applications
- Configuring JBoss Web Server
- Configuring URL paths
- Configuring connectors
- Configuring web class loading
- Configuring JavaServer Faces
The most common technologies for creating Java web applications are JSPs and servlets, the standard Java EE web component technologies. These technologies can be deployed to many different web containers, but the most popular is Apache Tomcat, the reference implementation for the servlet and JSP specifications. Tomcat also doubles as a general-purpose web server that’s able to do most things that popular native web servers (for example, Microsoft IIS and Apache HTTP Server) do, such as serving static content, supporting virtual hosting, supporting a Common Gateway Interface (CGI), and so on. Tomcat is written in Java, so it’s portable but historically slower at serving static web pages than native web servers. Apache is also the leader in the native web server market with the Apache HTTP Server, a fast and highly scalable web server.
JBoss AS serves web applications using a new Red Hat product called JBoss Web Server, which combines the speed of the Apache HTTP Server with the versatility of Apache Tomcat. JBoss Web Server is built on top of Apache Tomcat 6.0 but is capable of using a native Apache library called Apache Portable Runtime (APR) to attain the speed of the Apache HTTP Server.