At 9:54 AM -0800 3/16/05, Craig McClanahan wrote:
On Wed, 16 Mar 2005 04:33:12 -0800 (PST), Konstantin Priblouda
<[EMAIL PROTECTED]> wrote:

--- Ted Husted <[EMAIL PROTECTED]> wrote:

 > IMHO, Actions are fine the way they are. The one and
 > only problem is
 > that people keep trying to use Actions (and Struts)
 > as a component of
 > a business logic framework, rather than as an
 > *adjunct* to a business
 > logic framework.

 I'd like to disagree on this matter. Worst problem
 with struts actions is that they need to be derived
 from  basic actions.  This makes them pretty
 unflexible.

I agree with Ted, and the reasoning he states. Indeed, in this particular respect, Action *should* be inflexible because making it an interface would encourage you to use it incorrectly.

I disagree. Actions are not fine the way they are. They depend too directly on the Servlet API, which is one of the reasons they are too hard to unit test. All of the important support methods depend on an HttpServletRequest or the servlet property which is set at initialization time.


I understand the historical reason for these things being as they are, but that doesn't mean that there isn't room for improvement. These improvements don't all have to happen today, but I believe they can be made without sacrificing compatibility.

Joe

--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to