Servlet/Jakarta 3.0: What's New & Release History

What Is New in Servlet 3.0

Servlet 3.0 was a major overhaul that shifted how we build web applications on the JVM. It introduced a programming model centered around annotations and programmatic configuration, moving away from the rigid web.xml-only approach.

How did annotations change Servlet development?

Annotations eliminated the need for verbose XML descriptors for most common tasks. You can now declare a servlet, filter, or listener directly in the Java class file.

This means a servlet is defined with @WebServlet("/url") right above the class declaration. In practice, this drastically reduces the size and complexity of the web.xml file and makes code easier to understand and maintain.

Example

@WebServlet(urlPatterns = {"/hello"})
public class HelloServlet extends HttpServlet {
    // Servlet code
}

What are Web Fragments and pluggability?

Web Fragments allow frameworks and libraries to self-configure. A JAR file can contain a web-fragment.xml descriptor that gets automatically merged into the overall application configuration.

This matters because it enables true modularity. Frameworks like Jersey or Spring MVC can bundle their necessary servlets and filters without requiring you to manually copy-paste configuration into your main web.xml.

Why is asynchronous processing a big deal?

Asynchronous processing lets a servlet thread release itself back to the container to handle other requests while waiting for a long-running task to complete. This prevents thread starvation and improves scalability for I/O-bound operations.

You start async processing by calling request.startAsync(). This returns an AsyncContext which you use to complete the response later from another thread. It's essential for handling Comet or Ajax long polling efficiently.

Core Methods

AsyncContext aCtx = request.startAsync();
// ... pass context to another thread
aCtx.complete();

How does programmatic configuration work?

You can dynamically add servlets, filters, and listeners at runtime using the ServletContext API. This is done by implementing the ServletContainerInitializer interface.

This is powerful for framework developers. It allows for code-based configuration that can be more flexible than XML, enabling setups that adapt based on the environment or other conditions discovered at startup.

Were there any security enhancements?

Yes, Servlet 3.0 added a few security refinements. It introduced the HttpServletRequest.authenticate(), login(), and logout() methods for programmatic login.

This gives developers more control over the authentication process directly from their servlet code, complementing the existing declarative security model defined in the deployment descriptor.