Last checked and updated on 09 Jun 2026
What Is New in Servlet 2.3
Servlet 2.3 introduced foundational changes that moved the specification towards a more robust and configurable component model. The key updates focus on application lifecycle, filtering capabilities, and improved deployment options.
| Category | Changes |
|---|---|
| New Features | Servlet Filters, Application Lifecycle Events |
| Improvements | Enhanced WAR Deployment, Internationalization |
| Deprecated | Single Thread Model Interface |
How did Servlet 2.3 change application lifecycle management?
Servlet 2.3 added a proper application event listener model. This allowed components to react to the startup and shutdown of the entire web application, not just individual servlets.
You could now create listeners for ServletContextEvent and HttpSessionEvent. This was a game changer for initializing shared resources like connection pools or configuration settings when the app deployed.
What was the biggest new feature in Servlet 2.3?
The introduction of the Filter API was the headline feature. Filters finally provided a standardized way to intercept and transform requests and responses, a common need in web development.
Before filters, you had to hack this functionality into every servlet or use proprietary server extensions. The filter chain concept made it clean to handle things like logging, authentication, and compression in a reusable way.
public class LogFilter implements Filter {
public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain) {
// Pre-processing logic
chain.doFilter(req, res); // Invoke next filter/servlet
// Post-processing logic
}
}Did Servlet 2.3 improve how applications are packaged?
Yes, it formalized the Web Application Archive (WAR) structure. This made deployment more consistent across different servlet containers and reduced vendor-specific quirks.
The specification also added better support for internationalization, making it easier to build applications that could serve content in multiple languages based on client preferences.
What was deprecated in this version?
The SingleThreadModel interface was officially marked as deprecated. It was a flawed solution for thread safety that caused more problems than it solved by pooling servlet instances.
In practice, we never used it. Proper synchronization within service methods was always the correct approach for handling concurrent requests.
FAQ
Why are filters such a big deal in Servlet 2.3?
Filters solved a massive pain point. They provided a clean, modular way to implement cross-cutting concerns like security checks and logging without polluting your servlet code. This was a fundamental shift towards aspect-oriented programming in the servlet world.
How do application lifecycle events work?
You implement listener interfaces like ServletContextListener. The container calls contextInitialized when the app starts and contextDestroyed when it shuts down. This is where you'd initialize and clean up global resources.
Is the SingleThreadModel completely useless?
Pretty much. It was a well-intentioned but poorly designed attempt at thread safety. The interface creates instance pools that kill performance and don't actually solve shared state issues. Always handle thread safety explicitly instead.
Did 2.3 change how error handling works?
Not significantly in terms of API, but the enhanced deployment descriptors allowed for more declarative error page mapping. You could define specific error pages for different exception types and error codes in web.xml.
Was session management improved?
The core session APIs stayed the same, but the event listeners added HttpSessionListener and HttpSessionAttributeListener. This gave developers hooks to track session creation, destruction, and attribute changes for the first time.