You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Michael McGrady <mi...@michaelmcgrady.com> on 2004/04/28 18:33:50 UTC
Re: The future of actions (RE: Adding new Struts
features/sub-projects (was [Bug 28609] - Scriptable Actions
Support))
+1
At 09:06 AM 4/28/2004, Joe Germuska wrote:
>I don't think you're heretical at all, Martin. I was at the Wisconsin
>Java Software Symposium a couple of weeks ago, and between the sessions on
>WebWork and Spring and on writing testable Struts code, I came away
>convinced that changing how Actions work was a high priority.
>
>And, along the lines of what David says, I've been thinking about and
>writing about ideas for doing view-preparation in Struts for a while.
>
>To me these are two separate pieces -- I'm not sure if David and I see
>things differently, or if that's just how I read his words.
>
>I think we can make progress in this direction in a pre-2.0 time
>frame. In fact, given the way we work, I'm beginning to wonder if it
>makes sense to declare a 2.0 revolution; I think we can do a lot with
>incremental changes on the 1.x line.
>
>But the first steps are to get 1.2.1 out the door and get the TLP web site
>in order. Is there anything I can do to help with struts.apache.org? I
>don't really have a sense of the tasks, but if someone else does and wants
>to just dole a few out, I could try to help move that forward...
>
>Joe
>
>
>>--- Martin Cooper <ma...@apache.org> wrote:
>>
>><snip/>
>>
>>> Hmm. These days, I'm leaning towards thinking of Actions as something we
>>> retain for backwards compatibility only, once we're in a Struts 2.0
>>> world,
>>> so I'm not sure I'd consider a scriptable action, let alone just a plain
>>> Action, as something that would go in the core.
>>>
>>> I should probably elaborate a little on the perhaps heretical statement
>>> above. ;-)
>>>
>>> For a long time now, I have considered Actions as almost an
>> > anti-pattern.
>
>
>At 6:12 AM -0700 4/28/04, David Graham wrote:
>>I agree; I always found Tiles' Controllers to be more useful than Actions
>>for setting up a view because you attach the preparation code to the
>>actual view instead of trying to remember which URL causes this view to be
>>displayed. However, you can't always use a Tiles Controller and need an
>>Action to make decision logic. It would be nice to have a view
>>preparation system in the core and move away from Actions.
>
>--
>Joe Germuska
>Joe@Germuska.com
>http://blog.germuska.com
> "Imagine if every Thursday your shoes exploded if you tied them the
> usual way. This happens to us all the time with computers, and nobody
> thinks of complaining."
> -- Jef Raskin
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
>
>