Specifications

Chapter 14146
Dreamweaver architecture
When you use the Server Behavior Builder to create a Dreamweaver-specific extension,
Dreamweaver creates several files (EDML and HTML script files) that support inserting the
Server Behavior code into a Dreamweaver document (some behaviors also reference JavaScript
files for additional functionality). The architecture simplifies your implementation of the API and
also separates your runtime code from how Dreamweaver deploys it. This chapter discusses ways
of modifying these files.
Server behavior folders and files
The user interface for each server behavior resides in the Configuration/ServerBehaviors/
ServerModelName folder, where
ServerModelName is one of the following server types:
ASP.NET_Csharp, ASP.NET_VB (Visual Basic), ASP_Js (JavaScript), ASP_Vbs (VBScript),
ColdFusion (Dreamweaver MX compatible), JSP, PHP_MySQL, Shared (UltraDev 4
ColdFusion and Dreamweaver MX ColdFusion) or UD4-ColdFusion (Ultradev 4-compatible
ColdFusion).
Note: A distinction between Dreamweaver MX and Ultradev 4 ColdFusion compatibility is required because the
document type/server model for ColdFusion has changed since the release of Ultradev 4. For example, a server
behavior in Dreamweaver MX inserts CFML code that is different from the CFMLthat is inserted by the same server
behavior from Ultradev 4.
Extension Data Markup Language
Dreamweaver generates two EDML files when you use the Server Behavior Builder: a group EDML
file and a participant EDML file that correspond to the names that you provide in the Server
Behavior Builder. The group file defines the relevant participants, which represent code blocks, and
the groups define which participants are combined to make an individual server behavior.
Group files
Group files contain a list of participants, and participant files have all server-model-specific code
data. Participant files can be used by more than one extension, so several group files can refer to
the same participant file.
The following example shows a high-level view of the Server Behavior Group EDML file. For a
complete list of elements and attributes, see “Group EDML file tags” on page 160.
<group serverBehavior="Go To Detail Page.htm" dataSource="Recordset.htm">
<groupParticipants selectParticipant="goToDetailPage_attr">
<groupParticipant name="moveTo_declareParam" partType="member"/>
<groupParticipant name="moveTo_keepParams" partType="member"/>
<groupParticipant name="goToDetailPage_attr" partType="identifier" />
</groupParticipants>
</group>
In the groupParticipants block tag, each groupParticipant tag indicates the EDML
participant file that contains the code block to use. The value of the
name attribute is the
participant file name minus the .edml extension (for example,
moveTo_declareParam).
Participant files
A participant represents a single code block on the page, such as a server tag, an HTML tag, or an
attribute. A participant file must be listed in a group file to be available to a Dreamweaver
document author. A single participant file can be used by several group files.