You can try having a single servlet that has 'handlers' for it and so
all requests go through it first and it dipatches them further to
handlers. I have this setup and map the servlet to something like
/handler and then for an action such as handler/AuthenticationHandler
the request goes to
: Wednesday, July 24, 2002 1:39 PM
To: Tomcat Users List
Subject: RE: How to abort the webapp load/deployment
You could uild a MVC app where there are no page accesses
that don't pass through the controller (i.e. index.form and
form is mapped to a servlet which does a requestDispatcher
to index.html
On Mon, 29 Jul 2002, Extance, Paul wrote:
Date: Mon, 29 Jul 2002 09:54:46 -0700
From: Extance, Paul [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Subject: RE: How to abort the webapp load/deployment
I already use Struts, so
On Wed, 24 Jul 2002, Extance, Paul wrote:
Date: Wed, 24 Jul 2002 12:12:54 -0700
From: Extance, Paul [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: How to abort the webapp load/deployment
Hello,
Is it possible to write
You could uild a MVC app where there are no page accesses
that don't pass through the controller (i.e. index.form and
form is mapped to a servlet which does a requestDispatcher
to index.html or index.jsp). Have the controller only pass
people through if the validation has occured successfully.
