User Guide

292 Chapter 15: Server Behaviors
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 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.
Avoiding conflicts with share-in-memory JavaScript files
If several HTML files reference a particular JavaScript file, Dreamweaver loads the JavaScript into
a central location where the HTML files can share the same JavaScript source. These files contain
the following line:
//SHARE-IN-MEMORY=true
If a JavaScript file has the SHARE-IN-MEMORY directive and an HTML file references it (by using
the
SCRIPT tag with the SRC attribute), Dreamweaver loads the JavaScript into a memory location
where the code is implicitly included in all HTML files thereafter.
Note: Because JavaScript files that are loaded into this central location share memory, the files
cannot duplicate any declarations. If a share-in-memory file defines a variable or function and any
other JavaScript file defines the same variable or function, a name conflict occurs. When writing new
JavaScript files, be aware of these files and their naming conventions.