At 8:51 AM -0600 12/29/04, Joe Germuska wrote:
While driving back and forth for the holidays, I spent some time
thinking about Struts and the new chain framework. Here are a few
thoughts I had:
* ChainAction should be obsoleted before a 1.3.0 release in favor of
direct handling in the default
At 5:01 PM -0500 12/29/04, Sean Schofield wrote:
> This is definitely an interesting notion, and probably does belong in
Commons Chain itself.
Agreed.
To avoid any backwards compatibility issues, it might be easiest to add a
getCommand() method to CatalogFactory that
does this lookup (that ki
FYI
I moved this discussion to commons-dev in case anyone there wants to
contribute. (Hopefully nobody minds)
sean
On Wed, 29 Dec 2004 17:01:31 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> > This is definitely an interesting notion, and probably does belong in
> > Commons Chain itself.
>
> This is definitely an interesting notion, and probably does belong in
> Commons Chain itself.
Agreed.
> To avoid any backwards compatibility issues, it might be easiest to add a
> getCommand() method to CatalogFactory that
> does this lookup (that kind of method doesn't really fit into a cla
On Wed, 29 Dec 2004 08:51:54 -0600, Joe Germuska <[EMAIL PROTECTED]> wrote:
> [snip]
> * Now that we're moving around all these catalog/command pairs, I'm
> starting to wonder if we wouldn't like to have a standard
> representation of the pair in a single string. This may even belong
> in the chai
While driving back and forth for the holidays, I spent some time
thinking about Struts and the new chain framework. Here are a few
thoughts I had:
* ChainAction should be obsoleted before a 1.3.0 release in favor of
direct handling in the default chain. As was mentioned on the user
list, we
