The parameter names should match the ones that are specified in the insertion text and the
update parameters.
Parent
searchPattern
Type
Attribute.
Required
Yes.
Values
,
, ...
paramName1
paramName2
Each parameter name should be the exact name of a parameter that is used in the insertion
text. For example, if the insertion text contains
, you should define exactly one
@@p1@@
parameter with that name:
<searchPattern paramNames="p1">patterns</searchPattern>
To extract multiple parameters using a single pattern, use a comma-separated list of parameter
names, in the order that the subexpressions appear in the pattern. Suppose the following
example shows your search pattern:
<searchPattern paramName="p1,,p2">/(\w+)_(BIG|SMALL)_(\w+)/¬
</searchPattern>
There are two parameters (with some text in between them) to extract. Given the text:
, the first subexpression in the search pattern matches
"a"
, so
. The
<%= a_BIG_b %>
p1="a"
second subexpression is ignored (note the
in the
value). The third
,,
paramName
subexpression matches
"b"
, so
.
p2="b"
limitSearch
Description
This attribute limits the search to some part of the
tag.
whereToSearch
Parent
searchPattern
Type
Attribute.
356
Server Behaviors
Need help?
Do you have a question about the DREAMWEAVER 8-EXTENDING DREAMWEAVER and is the answer not in the manual?
Questions and answers