Deleting server behaviors

Default deletion and dependency counts The user can delete an instance that is selected in the Server Behaviors panel by clicking the Minus (-) button or pressing Delete. All the participants are removed except for the ones that are shared by other server behaviors. Specifically, if more than one server behavior has a participant pointer to the same node, the node is not deleted.

By default, participants are deleted by removing an entire tag. If the insert location is "wrapSelection", only the outer tag is removed. For attributes, the entire attribute declaration is removed. The following example shows an attribute participant on the ACTION attribute of a form tag:

<form action="<% my_participant %>">

After deleting the attribute, only form remains.

Using delete flags to limit participant deletion There might be cases where you want to limit the way that participants are deleted. This can be achieved by adding a delete tag to the EDML file. The following example shows a participant that is an href attribute of a link:

<a href="<%=MY_URL%>">Link Text</a>

When this attribute participant is deleted, the resulting tag is <a>Link Text</a>, which no longer appears as a link in Adobe Dreamweaver. It might be preferable to delete only the attribute value, which is done by adding the following tag to the participant EDML file:

<delete deleteType="innerOnly"/>

Another approach is to remove the entire tag when the attribute is deleted by typing <delete deleteType="tagOnly"/>. The resulting text is Link Text.