You'd do something like
req.getRequestDispatcher("/contextRel/path/to/logoutUrl").forward( req,
resp ). All of the request parameters available to the current servlet
would be passed on to the logout servlet.
--David
Peter Bauer wrote:
Am Donnerstag 18 Oktober 2007 schrieb Christopher Schultz:
Peter,
This next method call is the problem. I am sending a POST request from
one servlet instance to another one. But in situations with high load,
all 20 instances are busy, so the ActiveRoleRemoval.sendLogoutMessages
method which sends the POST request blocks because there is no other
instance/thread to process the request.
Is this quite possible or nonsense?
What if you use a RequestDispatcher.forward() instead of doing your own
POST? Is that an option? The current thread is always available ;)
-chris
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi cris,
how does this RequestDispatcher.forward() work? I would have to generate a new
HttpServletRequest and Response myself and send it to my Servlet URL, how
could this be done? Is it guaranteed to be received by the same servlet
instance?
br,
Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
