How to set session-timeout, error-pages programmatically without web.xml

Question

I am using Spring MVC and have successfully setup a WebApplicationInitializer (using Tomcat's ServletContainerInitializer), without any web.xml file. Adding filters (like Spring Security) and servlets (like Dispatcher) is no problem, and they work fine. I can also set init-params if I need to do so.

What I can't figure out is how to set up some of the special tags that normally exist in the web.xml. For example, I would like to set up a custom 403 error page. Usually I would do this in web.xml with:

<error-page>
    <error-code>403</error-code>
    <location>/accessDenied.html</location>
</error-page>

But I can't figure out how to do this inside the WebApplicationInitializer (which has access to the ServletContext).

I have the same problem with session-timeout and welcome-files. I've been searching for about two days, but still haven't seen this done programmatically. Again the goal is to completely remove the web.xml file and use the initializer class instead.

Any ideas?

score 7 · Accepted Answer · edited May 23 '17 at 12:09

7

Doesn't look like this is possible through WebApplicationInitializer, you will have to stick to web.xml for specifically this configuration along with some others listed with this question - Using Spring MVC 3.1+ WebApplicationInitializer to programmatically configure session-config and error-page

edited May 23 '17 at 12:09

Community

1
1

answered Jul 24 '12 at 17:21

Biju Kunjummen

49,138
14
112
125

Thanks. That does appear to be the case, based on the link in your answer. Bummer. – BobRob Jul 24 '12 at 20:00

score 1 · Answer 2 · answered Jan 11 '14 at 11:47

StandardEngine standardEngine = (StandardEngine)MBeanServerFactory.findMBeanServer(null).get(0).getAttribute(new ObjectName("Catalina", "type", "Engine"), "managedResource");

// This is totally irresponsible and will only work if this webapp is running on the default host
StandardContext standardContext = (StandardContext)standardEngine.findChild(standardEngine.getDefaultHost()).findChild(servletContext.getContextPath());

ErrorPage errorPage404 = new ErrorPage();
errorPage404.setErrorCode(404);
errorPage404.setLocation("/404");
standardContext.addErrorPage(errorPage404);

Which .jar is needed at compile time to access `org.apache.catalina.*` classes? — Stewart, Apr 05 '18 at 17:09

score 1 · Answer 3 · answered Feb 25 '16 at 20:10

You can use somethink like this:

@WebFilter(filterName = "ErrorPageFilter", urlPatterns = "/*")
public class ErrorPageFilter extends BaseHttpFilter {

private GlobalErrorHandler globalErrorHandler;

@Override
public void init(FilterConfig filterConfig) throws ServletException {
    globalErrorHandler = BeansUtil.getBean(filterConfig.getServletContext(), GlobalErrorHandler.class);
}

@Override
protected void doHttpFilter(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException {
    chain.doFilter(request, new ErrorPageHttpServletResponseWrapper(request, response));
}

private class ErrorPageHttpServletResponseWrapper extends HttpServletResponseWrapper {
    HttpServletRequest request;

    public ErrorPageHttpServletResponseWrapper(HttpServletRequest request, HttpServletResponse response) {
        super(response);
        this.request = request;
    }

    @Override
    public void sendError(int sc) throws IOException {
        globalErrorHandler.handleError(sc, request, this);
    }

    @Override
    public void sendError(int sc, String msg) throws IOException {
        sendError(sc);
    }
}
}

public interface GlobalErrorHandler {

void handleError(int responseCode, HttpServletRequest request, HttpServletResponse httpServletRequest) throws IOException;

void addHandler(int responseCode, String handlerDescription);
}

What is `BeansUtil` in this example? How does it extract your own invented `GlobalErrorHandler` from a `ServletContext` object? — Stewart, Apr 05 '18 at 17:04
Yes, it is a small util for getting beans from ServletContext by class. — Michael Starodynov, Apr 11 '18 at 13:07

score 0 · Answer 4 · edited May 23 '17 at 11:53

0

For page-error, see this answer: How to make a filter to detect if the user requested a page that is not found?

Make a Filter

Use HttpServletResponseWrapper and override the sendError() and setStatus()

Pass the wrapped response through chain.doFilter(req, wrapper)

If you get a sendError() in your wrapper, see if it's a 404.

Take appropriate response.

edited May 23 '17 at 11:53

Community

1
1

answered Dec 24 '15 at 08:12

auntyellow

2,423
2
20
47

How to set session-timeout, error-pages programmatically without web.xml

4 Answers4

Linked