This may be slightly OT, but not entirely...
I would like to suggest a change to what is being done in 1.3...
As I've mentioned before, I have a CoR implementation in JWP... I wrote
my own because Commons Chain didn't have some features I needed for a
project I was working on, and while I'm sure I could have modified it to
have those, it seemed easier to just write my own (and it was pretty
easy, so it worked out well). One of the decisions I made is that I
wanted to have a distinction between a Command and a Chain. I didn't
want a Chain=Command and Command=Chain as I believe is the case in
Commons Chain, right?
With that in mind, I'd like to see Struts have *two* attributes on the
Action mapping, "command" and "chain". Or alternatively, simply replace
"command" with "chain". In this way, people could make a declarative
distinction between the case where they are replacing an Action with a
Command, and the case where they are firing off a Chain in place of an
Action. More importantly, either change makes it clear what you are
actually executing. I mean, we look up chains in a catalog, not
commands, right? (except technically you *are* looking up a command, I
think conceptually for Struts developers that isn't an accurate
description though).
One of the things that people complain about with Struts is that some of
the config attributes don't really make much sense naming-wise... I
believe this may be a continuation of that complaint.
What are everyones' thoughts on this? I'd be happy to open a ticket and
submit patches, if there is any agreement.
Frank
Martin Cooper wrote:
On 2/19/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
Does "MyCommand" represent a chain in MyCatalog?
Yep.
If so, while I
wouldn't presume to speak for Craig, it sure seems like it :) I've
personally used the "fire a chain from an Action" in the past, but I can
certainly see where this would be very nice.
This is what I meant when I said earlier (in this thread) that I don't have
any Action classes in my 1.3 app. I don't need 'em any more, even just to
invoke a chain.
--
Martin Cooper
Frank
Martin Cooper wrote:
On 2/19/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
<snip/>
The next step would be to provide customizable chains per Action
(becoming
even more like how you configure actions in WebWork) -- but you can
even
do
that today by using an Action that itself executed a chain.
Craig, isn't that what we already have with:
<action path="/MyAction"
catalog="MyCatalog"
command="MyCommand"/>
or am I misunderstanding?
--
Martin Cooper
Michael.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
