Changes between Initial Version and Version 1 of HowTos/HowToUseScaffolds/AddingSpecificEventHandlers

Timestamp:

04/15/09 19:43:29 (17 years ago)

Author:

trac (IP: 127.0.0.1)

Comment:

--

HowTos/HowToUseScaffolds/AddingSpecificEventHandlers

@@ +1 @@
+= Adding Specific Event Handlers =
+
+By default, the <scaffold> tag adds five event-handlers: ''table''.list, ''table''.view, ''table''.edit, ''table''.commit, ''table''.delete.
+
+However, you may not want all of these added by default. To adjust the list of scaffolds to automatically create, change the value of the !DefaultScaffolds property of the !ModelGlueConfiguration bean in !ColdSpring.xml. For example, to only automatically create view and list scaffolds, the tag would be changed to the following:
+
+{{{
+<property name="defaultScaffolds"><value>list,view</value></property>
+}}}
+
+Edit, commit, delete, and delete scaffolds are still available, but would need to be specified in the scaffold tag's TYPE attribute (see below).
+
+== Using the TYPE attribute ==
+
+For a given scaffold tag, you may specify the list of event-handlers to create by using the TYPE attribute of the scaffold tag. This is especially useful for applying functionality such as security.
+
+For example, in a given application where anyone can view contacts but only administrators can update contacts, we could use the following XML in !ModelGlue.xml to protect the edit, commit, and delete event handlers from unauthorized access (assuming a message listener for "!UserMustBeAdministrator" performs security functionality and adds a result named "!SecurityViolation" in the event of bad access):
+
+{{{
+<scaffold object="contact" type="list,view" />
+
+<scaffold object="contact" type="edit,commit,delete">
+
+<broadcasts>
+
+<message name="UserMustBeAdministrator" />
+
+</broadcasts>
+
+<results>
+
+<result name="SecurityViolation" do="SecurityViolation" redirect="true" />
+
+</results>
+
+</scaffold>