Hello I'm working on pax-web-undertow in particular, but I have general issue with error pages, welcome files and similar resources.
There's for example https://ops4j1.jira.com/browse/PAXWEB-1032 "Strange handling of welcome files". It's better with pax-web-extender-war, because the unit of deployment is analogous to web.xml file which, even if empty (no servlets, filters, error pages, ...) is handled effectively by RegisterWebAppVisitorWC or RegisterWebAppVisitorHS. The first one does: webContainer.registerResources("/", "default", httpContext); The second one does: httpService.registerResources("/", "", httpContext); Regardless of what is found in the deployment descriptor (or in org.ops4j.pax.web.extender.war.internal.model.WebApp) What do you think if we change the implementation, so "default" servlet is *always* registered? For example with Undertow, without default servlet there's no ... servlet to handle the request where no path matches, so no *servlet resource* can send 404 error, so error pages can't be invoked. There's simple low-level HttpHandler that simply sends 404 without involving error pages (and anything from servlet specs in general). I'll experiment with having *default servlet* by default. regards Grzegorz Grzybek -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
