>>Given that chaining actions is a bad practice, for reasons that I've stated
>>many times before,
I'm not really interested in providing support to encourage people to use that
pattern.
Me neither. I've written many times on the boards why I don't like the chaining
pattern either.
The good news is, that's not what this enhancement is! This proposal is about
naming your actions
so that you can refer to them in other forwards. So if you have an action named
"foo" you can
forward directly to "foo" without having to re-write the action path again. I
hope this clears up
your confusion -- it's not chaining, it's resolution.
>> Also, there is an XML-related reason that we don't use the 'id' attribute in
>> the Struts config
files, although it is defined. Unfortunately, it's too early and I haven't had
coffee yet, so that
reason escapes me right now.
W3C has a proposal to make the ID attribute a reserved attribute for all tags,
to uniquely
identify them in a document. This fits perfectly into this schema, since you
would logically would
never have duplicate action names.
I would have liked to chosen a different attribute (like name), but
unforunately the <action> and
<forward> tags do not synch. The [EMAIL PROTECTED] refers to the bean you want
to use, and the
[EMAIL PROTECTED] refers to its, well, name. Once I noticed this, it looked
confusing; so I settled on
"id" as an acceptable attribute name.
-- Paul
__________________________________
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
