@ Dan - Yes, separate form and form processing events are mandatory, imo. I intended that to be implied by my short snippet, but perhaps it was not inferred. :-)
@ Charlie - Thanks for the link. 'Twas a good read. :-) @ Dennis - Thanks for pointing out a couple of things that I had not even thought of: 1. An event handler can ignore a result issued by a controller by not defining a named <result> element for it. 2. One situation where I do use forward() is security controllers, because many of my event handlers must broadcast security messages and all security violations are redirected to the same event in the application. Using forward() saves me from having to scatter something like <result name="notAuthorized" do="security.accessDenied" redirect="true" /> all around my ModelGlue.xml. I do however support an optional message argument to let event handlers forward security violations to a different event. @ All - I was leaning heavily toward the <result /> method, for many of the reasons you guys have mentioned, and it appears that I am in good company with that thinking. :-) -- 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
