Specifications

ManualsBrandsMACROMEDIA ManualsOtherDREAMWEAVER 8-DREAMWEAVER API

181

182

183

184

185

186

187

188

189

190

Server Behaviors 187

This server behavior no longer works correctly because only one parameter is named total. To

solve this problem, make sure that there is a parameter with a unique value and can be used to

match the participants. In the following example, you could make the

total variable name

unique using the column name:

<% itemPrice_total = Recordset1.Fields.Item("itemPrice").¬

Value * 1.0825 %>

<% salePrice_total = Recordset1.Fields.Item("salePrice").¬

Value * 1.0825 %>

<html>

<body>

The total (with taxes) is $<%=itemPrice_total%>

Sale price (with taxes) is $<%=salePrice_total%>

</body>

</html>

The search patterns now uniquely identify and match the participants.

Search pattern resolution

Dreamweaver MX supports the following actions by using the participant

searchPatterns functionality:

• File transfer dependency

• Updating the file paths for any file reference (such as those for include files)

When Dreamweaver MX creates server models, it builds lists of patterns by scanning all the

participants for special

paramNames. To find URLs to check file dependency and to fix the

pathname, Dreamweaver MX uses each

searchPattern tag in which one of the paramNames

attribute ends with

_url. Multiple URLs can be specified in a single searchPattern.

For each translator

searchPattern that has a paramNames attribute value that ends with

_includeUrl, Dreamweaver MX uses that searchPattern to translate include file statements on

the page. Dreamweaver MX uses a different suffix string to identify include file URLs because not

all URL references are translated. Also, only a single URL can be translated as an include file.

In resolving a

searchPatterns tag, Dreamweaver uses the following algorithm:

1 Look for whereToSearch attribute within the searchPatterns tag.

2 If the attribute value starts with tag+, the remaining string is assumed to be the tag name (no

spaces are allowed in the tag name).

3 Look for limitSearch attribute within the searchPattern tag.

4 If the attribute value starts with attribute+, the remaining string is assumed to be the

attribute name (no spaces are allowed in the attribute name).

If these four steps are successful, Dreamweaver MX assumes a tag/attribute combination;

otherwise, Dreamweaver starts looking for

searchPattern tags with a paramName that has a

_url suffix and a regular expression that is defined. (For information about regular expressions,

see the “Regular expressions” on page 158.)

The following example of a

searchPatterns tag has no search pattern because it combines a tag

(

cfinclude) with an attribute (template) to isolate the URL for dependency file checking, path

fixing, and so forth:

</searchPatterns>