The only normal situation where every method in the lifecycle would get called twice is if you are doing "action chaining" -- the returned ActionForward from one Action.execute() call points at a path that is another Action, rather than being a JSP page or something in your view tier. In such a case, the entire lifecycle will get executed again for the second Action.
Craig
On Thu, 28 Oct 2004 15:15:39 +0200, Marco Rossi <[EMAIL PROTECTED]> wrote:I try to extend the default RequestProcessor, only to view the call sequence.
Something like this, for every method of the RP:
protected boolean processPreprocess(HttpServletRequest request,HttpServletResponse response) { logger.debug("processPreprocess"); return true; }
I saw that every method is call two times. Why?
Craig's explanation would describe a situation where the preprocess method is called twice with some time in between.
If you are seeing the messages appear twice in immediate succession, you may have misconfigured your logger. At least, if you are using log4j, if you accidentally assign an appender twice, you'll get duplicate messages. The most frequent cause of this is explicitly configuring a logger to use the same appender that you are also using for the root appender.
Apologies if this is totally off track from what you're seeing.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
