Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <1083AAE7-BE31-4921-B984-68D2695C2034@tchijov.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Tomcat Users List <users@tomcat.apache.org>
From: Andrei Tchijov <andrei@tchijov.com>
Subject: Using RequestDispatcher.include() outside of Request/Response cycle.
Date: Tue, 9 Oct 2007 16:48:10 -0400

Hi,
   I have a valve which detects some events in life-cycle of a web  
application ( like successful login/failed login/logout ) and invokes  
some configurable JSP page to let it perform some audit auctions  
( like putting records in the table which trace access to  
application ).  It works fine, the only problem is auditing session  
timeouts.  I can (and do) add session listener, so it is not a  
problem to detect that session timed out. The problem is how to  
invoke my audit JSP page. RequestDispatcher.include() require Request  
and Response objects which are obviously not accessible inside  
SessionEvent callback.  Should I create some sort of "fake" Request/ 
Response objects? Can I reuse some Request/Response objects from  
earlier (like when valve detected creation of the session)?  Audit  
JSP page does NOT produce any output and it does NOT require any  
information from Request, so this Request/Response objects only need  
to be able to make RequestDispatcher.include() happy.
   Your thoughts will be highly appreciated,

Andrei Tchijov

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org