Sling seems to take over all JSP page processing, so JSP pages now
have to remain in the repository?
What's the easiest way to enable the servlet container to retain
processing requests which are not handeled by the sling servlet? I
know it's technically possible to do programmatically with tomcat using
RequestDispatcher disp =
request.getSession().getServletContext().getNamedDispatcher("default");
disp.forward(request, response);
but it would be nice if this could be done using simple configuration.
Would be very handy when integrating sling into an existing web
application which needs to retain JSP processing by the servlet
container.
--
Torgeir Veimo
[EMAIL PROTECTED]
