Hello All, I think I am getting closer to being able to use m2 effectively, however I have some questions about filters and the duration (scope) of event.args variable.
Both are pretty simple, but I need some clarification. It looks to me that filters are used for validation and decision making. Is this accurate? The way I am looking at it is this way: Form submit event -> form validation filter -> form listener -> results page Basically you have a form, it gets submitted, it goes to the filter for validation and if it passes validation (which would return false, thus stopping that event from further processing) it send the data to the listener event which does something and after that completes sends you to a results or confirmation page (depending on what you are trying to do). Well from my understanding, if the filter returns true (basically failing the validation) the event can announce another event which might be something like message about how you filled out the form incorrectly, etc. If that is true, is it possible to access the event.args structure and return the data to the form so the user does not have to type it all back in? How long does the event.args structure remain in memory? Does it remain until you have another event that puts data into the event.args structure? Thanks! -- You received this message because you are subscribed to Mach-II for CFML list. 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/mach-ii-for-coldfusion?hl=en ***New URLs as of April 29th, 2010*** SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
