On Sat, Nov 21, 2009 at 5:08 AM, Bob Silverberg <[email protected]> wrote: > Right, but maybe, and this is just a Bob-Crazy-Idea-Maybe, what if, in > addition to storing the result in _variables.results in the EventContext > from whence it's used for processing results, it was also added to a > "reporting array" of results in the event as well? So I wouldn't call > getResults() to find out what results have been added to an event, rather I > could call event.getValue("addedResults") which would return an array of any > and all results that had been added?
And when a redirect is used all that would have to be saved across the redirect too... It also ties views directly to controller/XML logic which seems like a bad idea in my mind. Having a view displaying an optional error message, pulled from the event objects seems much better architecture to me. Then the view neither knows nor cares how it got there. -- Sean A Corfield -- (904) 302-SEAN Railo Technologies US -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en
