Variables

Methods

Data types

Operators

Input / output

Control Flow

Type conversion

Casting

Arrays

Classes

Interfaces

Generics

Exceptions

Packages

JAR files

Autoboxing

Access Levels

Keywords

I/O

Concurrency

Reflection

Serialization

RMI (remote method invocation)

Annotation

Lambda expressions

Collections Framework

JDBC

In general, the Apache HTTP server is just a plain old web server designed to serve static web pages. There are plenty of modules which can be installed to enhance Apache's abilities so that it can serve dynamic webpages using various technologies such as PHP, CGI or whatever, but the core of Apache is just a plain old HTTP server. Tomcat, on the other hand, is specifically designed from the ground-up to serve as a Java Servlet engine. It's primary purpose is to implement the Java Servlet API and execute Java servlets for the purpose of building dynamic websites. Tomcat can also be used as a regular HTTP server that serves static pages, but that is not its primary purpose. (Also, Tomcat is allegedly slower than Apache httpd when it comes to serving static pages.) The two technologies can be used together through a connector module called mod_jk. This will allow you to use the Apache HTTP server to serve regular static webpages, and the Tomcat Servlet engine to execute servlets.

Fork

Clone

Download as ZIP file

Pull request