✅ Short answer:

Servlet 3.0 (finalized in December 2009, part of Java EE 6) brought major improvements to simplify development and support modern web applications.

---

✅ Main Features introduced in Servlet 3.0:

Feature	Description
1. Annotation-based Configuration	No more messy web.xml! You can declare servlets, filters, listeners with annotations like @WebServlet, @WebFilter, @WebListener.
2. Pluggability	Web apps can bring their own servlets/filters/listeners in their own JARs — the container auto-scans for annotations.
3. Asynchronous Processing (Async Servlet)	Servlets can handle long-running tasks without blocking threads → super important for scalability (ex: chat apps, long polling).
4. Programmatic Configuration	You can add servlets, filters, listeners dynamically at runtime (inside ServletContextListener).
5. File Upload Support (Multipart)	Built-in support for handling file uploads (@MultipartConfig, request.getPart()), no need for third-party libraries like Apache Commons FileUpload anymore.
6. Security Enhancements	Programmatic login/logout (HttpServletRequest.login(), logout()), better declarative security options.

✅ Let’s explain each feature a little more:

1. Annotation-based Configuration

Before Servlet 3.0:

• You had to declare everything inside a huge web.xml file.

After Servlet 3.0:

• You can just annotate your classes:

import jakarta.servlet.annotation.WebServlet;

@WebServlet("/hello")
public class HelloServlet extends HttpServlet {
    // no need to touch web.xml
}

Similarly for Filters:

@WebFilter("/*")
public class MyFilter implements Filter { }

Listeners:

@WebListener
public class AppContextListener implements ServletContextListener { }

2. Pluggability

• You can drop JARs inside WEB-INF/lib/, and if those JARs have servlets, filters, or listeners annotated → container automatically discovers and loads them.
• Very useful for modular apps or frameworks!

3. Asynchronous Processing

New in Servlet 3.0: Async Servlet API!

• Traditionally, servlet processing was strictly synchronous: one request → one thread.
• Now you can startAsync() to free the thread and do background work.

Example:

@WebServlet(urlPatterns = "/async", asyncSupported = true)
public class AsyncServlet extends HttpServlet {
    protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException {
        AsyncContext asyncContext = req.startAsync();
        
        asyncContext.start(() -> {
            try {
                // Do some long running work
                Thread.sleep(3000);
                asyncContext.getResponse().getWriter().write("Async work done!");
                asyncContext.complete();
            } catch (Exception e) {
                e.printStackTrace();
            }
        });
    }
}

Benefit: server thread is not blocked during slow work → better scalability.

4. Programmatic Configuration

In ServletContextListener, you can now register servlets, filters, listeners programmatically without annotations or web.xml.

Example:

public class AppInitializer implements ServletContextListener {
    @Override
    public void contextInitialized(ServletContextEvent sce) {
        ServletContext ctx = sce.getServletContext();
        
        ServletRegistration.Dynamic myServlet = ctx.addServlet("myServlet", new MyServlet());
        myServlet.addMapping("/dynamic");
    }
}

Use case: dynamic modules, plugins, or runtime decisions.

5. File Upload Support

No more external libraries needed!

You can declare:

@WebServlet("/upload")
@MultipartConfig
public class UploadServlet extends HttpServlet {
    protected void doPost(HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException {
        Part filePart = request.getPart("file");
        InputStream fileContent = filePart.getInputStream();
        // process the file
    }
}

Built-in, simple, clean!

6. Security Enhancements

• Programmatic login:

request.login(username, password);

Programmatic logout:

request.logout();

No need to always depend on form-based login configuration.

Also improved session tracking, declarative security options.

✅ Quick Summary Table

Feature	Why it matters
Annotations	Simplifies configuration, no more huge web.xml
Pluggability	Modular web apps become easy
Async Servlets	Scalable, non-blocking web apps
Programmatic config	Dynamic registration possible
File Upload built-in	Easy file uploads
Security improvements	Programmatic login/logout control

---

🌟 Visual Timeline:

Servlet 2.x → Everything in web.xml → synchronous only → complicated file upload
        ↓
Servlet 3.0 → Annotations → Async → Programmatic → Built-in File Upload → Easier Security

✅ Bonus: Servlet 3.1 (later) added WebSockets and non-blocking IO, but that’s after Servlet 3.0!