How can errors be handled on JSP pages?

In JSP, errors can be handled in several ways:

Using the <%@ page errorPage="url" %> directive: This is the most common method. On the page where an error might occur, specify the URL of the error handling page.
```
<%@ page errorPage="/errorPage.jsp" %>
```
On the /errorPage.jsp page, you need to include the directive <%@ page isErrorPage="true" %> to access the exception object.
```
<%@ page isErrorPage="true" %>
<html>
<head><title>Error</title></head>
<body>
    <h1>An error occurred</h1>
    <p>Error message: <%= exception.getMessage() %></p>
</body>
</html>
```

Using the <error-page> element in web.xml: This is a more centralized approach. In the deployment descriptor web.xml, you can configure error routing based on exception type or HTTP status code.

<web-app>
    <error-page>
        <exception-type>java.lang.ArithmeticException</exception-type>
        <location>/errors/arithmeticError.jsp</location>
    </error-page>
    <error-page>
        <error-code>404</error-code>
        <location>/errors/notFound.jsp</location>
    </error-page>
    <error-page>
        <exception-type>java.lang.Throwable</exception-type>
        <location>/errors/generalError.jsp</location>
    </error-page>
</web-app>

On the pages specified in <location>, you should also include the directive <%@ page isErrorPage="true" %>.

Using try-catch blocks in scriptlets: While less preferred for complex logic, for simple cases, you can wrap potentially error-throwing code in a try-catch block.

<%
try {
    int result = 10 / 0; // Code that may cause an error
    out.println("Result: " + result);
} catch (ArithmeticException e) {
    out.println("Arithmetic error occurred: " + e.getMessage());
}
%>

Using Servlet filters: Filters can intercept requests and responses, including errors. In a filter, you can redirect to an error page or perform other error handling logic.

// Example Filter for error handling
public class ErrorHandlingFilter implements Filter {

    @Override
    public void init(FilterConfig filterConfig) throws ServletException {
    }

    @Override
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain)
            throws IOException, ServletException {
        try {
            chain.doFilter(request, response);
        } catch (Throwable e) {
            // Log the error
            // Redirect to error page
            request.setAttribute("errorMessage", e.getMessage());
            request.getRequestDispatcher("/errors/generalErrorHandledByFilter.jsp").forward(request, response);
        }
    }

    @Override
    public void destroy() {
    }
}

Filter configuration in web.xml:

<filter>
    <filter-name>errorHandlingFilter</filter-name>
    <filter-class>com.example.ErrorHandlingFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>errorHandlingFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

The choice of method depends on the required level of centralization, complexity of logic, and developer preferences. The most common and recommended methods are using <%@ page errorPage="..." %> and <error-page> in web.xml.