Patrick Lightbody wrote:
I found a possible way around this, but I'm not sure if it's a good idea or
not :)
What if the FilterDispatcher never actually makes a call to
filterChain.doFilter()? This would get around the duplicate view request
problem outlined below, but would require that the
I don't plan on using it, so as long as it doesn't mess up the core +1
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 2:37 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] WebWork 2.0: FilterDispatcher?
[Small problem
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 23, 2003 1:33 AM
Subject: Re: [OS-webwork] WebWork 2.0: FilterDispatcher? [Small problem]
Found one small problem with this approach (and it may just be that using
the filter + the servlet at all times just can't always work perfectly
Found one small problem with this approach (and it may just be that using
the filter + the servlet at all times just can't always work perfectly):
If you are using the filter and servlet and access success.jsp, the action
will be invoked, then the ResultInterceptor will kick in, call
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED]]
Thoughts? One way would be to make the WW 2.0
framework/config more rigid and to remove the
ResultInterceptor stuff and specifically hard code the
ServletDispatcher to doing the dispatching _in_ the servlet
