All Known Implementing Classes:
StandardValveContext
A ValveContext is the mechanism by which a Valve can trigger the
execution of the next Valve in a Pipeline, without having to know anything
about the internal implementation mechanisms. An instance of a class
implementing this interface is passed as a parameter to the
Valve.invoke() method of each executed Valve.
IMPLEMENTATION NOTE: It is up to the implementation of ValveContext to ensure that simultaneous requests being processed (by separate threads) through the same Pipeline do not interfere with each other's flow of control.
Craig - R. McClanahanGunnar - RjnningPeter - Donald$ - Revision: 1.3 $ $Date: 2007/05/05 05:31:52 $| Method from org.apache.catalina.ValveContext Summary: |
|---|
| getInfo, invokeNext |
| Method from org.apache.catalina.ValveContext Detail: |
|---|
|
invoke() method of the next Valve that is part of
the Pipeline currently being processed (if any) to be executed, passing
on the specified request and response objects plus this
ValveContext instance. Exceptions thrown by a subsequently
executed Valve (or a Filter or Servlet at the application level) will be
passed on to our caller.
If there are no more Valves to be executed, an appropriate
ServletException will be thrown by this ValveContext. |