Hello David.
I don't know if this will help you, but when we needed to perform some
basic functionality prior to each page request we created a super-class
for our servlets (actually it was jhtml, not JSP, but it was a while
ago).
This super class was a servlet that implemented the method
service(req,resp), and in that method we did some important global
things. We tracked page level security, guaranteed a single thread per
session (by synchronizing on the session object), and then after/within
that logic we called super.service(req,resp) which then went on to run
the appropriate page for us. (This requires that your JSPs (or servlets
if you write the controller separately as I'd suggest) extend this
intermediary class which would in turn extend HttpJspBase.
I'm not sure if I've explained it very well. I'd be happy to write a
better description if you'd like one. Please feel free to email me
directly at [EMAIL PROTECTED]
Assuming that I've described it well enough that it's recognizable, has
anyone else out there used this approach?
-Vik
"Aiken, David" wrote:
>
> > hi all..
> >
> > We're hitting a problem with the MVC approach in tomcat.
...
--
Vik P. Solem [EMAIL PROTECTED] 781-344-1133
VikTech Systems Inc. Built right, now.
http://www.viktech.com
