Don
Dakota Jack wrote:
<snip>
On Sun, 13 Feb 2005 14:05:11 -0800, Don Brown
I don't mind sticking ActionContext everywhere as it is better than having the code rely directly on the servlet api, but since we are talking about modifying Action, why not get rid of this "must extend Action" stuff and make Action an interface? IMO, Struts core should depend on this new interface, say Actionable, where Action would be an implementation of this interface. Since the methods of Action like saveMessages have been moved to ActionContext, we can safely get rid of Action, a passing I won't soon be missing. :)
Don
</snip>
I would definitely support all of this and look forward to all of it, except the name "Actionable". First, the interface is not a tag interface, is it? If the "able" is something you are really fond of, then I would suggest, in honor of Craig calling it "Doable". Second, and related, the pejorative nature of "Actionable" is unfortunate, don't you think?
Main Entry: ac·tion·able Pronunciation: 'ak-sh(&-)n&-b&l Function: adjective : subject to or affording ground for an action or suit at law - ac·tion·ably /-blE/ adverb
Could the interface be called "Action"? I imagine this has all been discussed before and will set off a firestorm of "Lordy Lordy"s. But, what the heck, one can keep trying to be helpful.
Jack
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
