Dreamweaver Architecture - MACROMEDIA DREAMWEAVER MX 2004-EXTENDING DREAMWEAVER Manual

Note: For information about participants, participant groups, and how Dreamweaver EDML files are
structured, see "Extension Data Markup Language" on page

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 (UI) 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, JSP, PHP_MySQL, or Shared (cross-server model implementations).
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 corresponding 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 serverBehavior="Go To Detail Page.htm" dataSource="Recordset.htm">
<groupParticipants selectParticipant="goToDetailPage_attr">
<groupParticipant name="moveTo_declareParam"
<groupParticipant name="moveTo_keepParams"
<groupParticipant name="goToDetailPage_attr" partType="identifier" />
</groupParticipants>
</group>
In the
groupParticipants
participant file that contains the code block to use. The value of the
participant file name minus the .edml extension (for example, the
attribute).
248 Chapter 15: Server Behaviors
"Group EDML file tags" on page
block tag, each
groupParticipant
248.
262.
partType="member"/>
partType="member"/>
tag indicates the EDML
attribute is the
name
moveTo_declareParam