Costin Manolache wrote:
Remy Maucherat wrote:
The time is mostly parsing web.xml. However, it's nothing when
compared to starting certain webapps (such as the admin webapp),
where *one* webapp takes more time than starting up the rest of
Tomcat (including all the simple webapps, JMX and the
Remy Maucherat wrote:
One simple solution is to add
% // Force the initialization of action servlet
RequestDispatcher
actionS=getServletContext().getNamedDispatcher(action).include(request,response);
%
in login.jsp
This seems good enough already.
Ok, I'll check it in then after I figure out
Costin Manolache wrote:
Remy Maucherat wrote:
BTW, does the spec says that the form login page is excluded from
filters ??
That's undefined, as it's some kind of internal dispatching of the
container. It seemed reasonable trying to do it with a RD forward.
Well, if I have a filter on /* and / (
Remy Maucherat wrote:
Costin Manolache wrote:
Remy Maucherat wrote:
BTW, does the spec says that the form login page is excluded from
filters ??
That's undefined, as it's some kind of internal dispatching of the
container. It seemed reasonable trying to do it with a RD forward.
Well, if I have
Remy Maucherat wrote:
The time is mostly parsing web.xml. However, it's nothing when
compared to starting certain webapps (such as the admin webapp),
where *one* webapp takes more time than starting up the rest of
Tomcat (including all the simple webapps, JMX and the modeler
descriptors, etc).
