Yes..with Servlet 2.3 you could have a filter before the request is handled,
and before the response goes back, that would "check and/or set" the flag,
and "remove" the flag on the way back. But then..that would tie you to
Servlet 2.3 spec..which I don't know of any server that fully implements it
just yet, and its still a ways away before its widely used. I'd say a good
year or more before Servlet 2.3 is adopted, as J2EE 1.3 wont be out until
early next year.
> > What I thought of doing is half way there. When a request comes
> in, store
> an
> > attribute in the HttpSession that flags a "transaction"
> (transaction being
> > either a database hit, or just a simple request..period) is activated.
> This
> > would only work with an MVC framework though..it would require the
> > ControllerServlet to "check" every single request if this attribute
> existed.
>
>
> I cannot help on the rest of the issue, but I would think a ServletFilter
> could do this job also.
>
> ==================================================================
> =========
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set
> JSP-INTEREST DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
