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 <[EMAIL PROTECTED]> wrote:
<snip/>
> anti-pattern.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
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]