I was fishing for an answer more like this:
By applying an event type to a group of events instead of individual
events the xml becomes easier to understand at a glance. Improved code
comprehension makes for faster and easier application maintenance by
developers unfamiliar with an application. Removing the repetitive type
declaration makes code refactoring easier and less error prone.
Grouping handlers by type makes David less likely to accidentally expose
administrative functions without password protection. An example usage
could look something like this:
| <event-types>
<event-type name="SecuredEvent">
<before>
<broadcasts>
<message name="LoginRequired" />
</broadcasts>
<results>
<result name="NotLoggedIn" do="user.login" />
</results>
</before>
</event-type>
</event-types>
<event-handlers defaultType="SecuredEvent">|
| <event-handler name="admin.administrate">|
| <broadcasts>|
| <message name="AdminIsDoingStuff" />|
| </broadcasts>|
| <views>|
| <include name="body" value="admin.cfm" />|
| </views>|
| </event-handler>|
| |
| ...|
|
</event-handlers>|
|
<event-handlers>|
| <event-handler name="home.page">|
| <views>|
| <include name="home" value="home.cfm" />|
| </views>|
| </event-handler>|
| ...|
| </event-handlers>|
--~--~---------~--~----~------------~-------~--~----~
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
For more about Model-Glue, check http://www.model-glue.com .
-~----------~----~----~----~------~----~------~--~---
