And at workstations the world over is heard the sound of caps flipping from
bottles of Guiness Stout, Sam Adams, and the occasional Molson Gold. :)
-T.
On Mon, 20 Dec 2004 23:30:31 -0800, Don Brown wrote:
> As you may have noticed, I've completed the merge of struts-chain
> with Struts core (see
At 9:13 AM -0800 12/21/04, Martin Cooper wrote:
On Mon, 20 Dec 2004 23:30:31 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
As you may have noticed, I've completed the merge of struts-chain with
Struts core (see the commit message for details). I would like to add
this is meant as a step forward,
On Mon, 20 Dec 2004 23:30:31 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
> As you may have noticed, I've completed the merge of struts-chain with
> Struts core (see the commit message for details). I would like to add
> this is meant as a step forward, not as my ultimate vision for how
> things sh
ComposableRequestProcessor replaces RequestProcessor in Struts 1.3.x.
RequestProcessor is still available and could be used by specifying the
className in the controller config.
Struts 1.2.6 is the latest development release and Struts 1.2.4 is the
latest stable release, but all new development
I'm still a little fuzzy on the roadmap for struts. Now that
struts-chain is in the core, does this mean we are moving towards
using struts-chain over the current RequestProcessor? If so, what
version is this anticipated to happen by? Finally, what is the branch
being used for right now?
TIA to
As you may have noticed, I've completed the merge of struts-chain with
Struts core (see the commit message for details). I would like to add
this is meant as a step forward, not as my ultimate vision for how
things should be, meaning if someone doesn't like a configuration
property name or pro
