I've finished the first pass at a plugin that collapses the zero-config
and code-behind as well as adds support for components that have actions
in other JAR files. Here are the highlights:
- Uses action packages to locate actions
- Pre-loads all the results it can find via the ServletContext
I think perhaps it warrants a bit of discussion because if I were going
to tackle it I might be inclined to suggest that the struts-plugin.xml
be converted from an XWork configuration file to a new XML format that
would have a section specifically for XWork configuration and a
separate
section
Could this be related to WW-1816 FitlerDispatcher not always calling
ActionContextCleanUp.cleanUp(Request)?
--- John M Flinchbaugh <[EMAIL PROTECTED]> wrote:
> Synopsis:
> FilterDispatcher may not cleanup completely and causes the
> StrutsRequestWrapper to be omitted in some executions (race con
Synopsis:
FilterDispatcher may not cleanup completely and causes the
StrutsRequestWrapper to be omitted in some executions (race condition).
Adding ActionContextCleanUp filter seems to alleviate the issue. As
advertized, I'd expect FilterDispatcher to be able to function on its
own.
Long story:
I
Ted Husted wrote:
On 5/1/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
I think perhaps it warrants a bit of discussion because if I were going
to tackle it I might be inclined to suggest that the struts-plugin.xml
be converted from an XWork configuration file to a new XML format that
would ha
On 5/1/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
I think perhaps it warrants a bit of discussion because if I were going
to tackle it I might be inclined to suggest that the struts-plugin.xml
be converted from an XWork configuration file to a new XML format that
would have a section specifi
