Using Parameters In Server Behaviors - MACROMEDIA DREAMWEAVER MX 2004-USING DREAMWEAVER Use Manual

You can specify additional information about the server you are creating by using the Advanced
11
options panel.
Click the Advanced button to display more options.
12
If you need to create more code blocks, repeat steps 7 through 13 as needed.
13
If the server behavior requires that parameters be supplied to it, you will need to create a dialog
14
box that accepts parameters from the person applying the behavior.
To create a dialog box that accepts user input parameters, see
custom server behavior" on page
After you have performed the above steps as required by the server behavior you are creating,
15
Click OK.
Once you create a server behavior, it is listed in the Server Behaviors panel. Test the server
behavior and ensure that it functions properly.
Related topics
•
"Positioning code blocks" on page 602
•
"Repeating code blocks" on page 594
•
"Coding guidelines" on page 596
•
"Positioning code blocks" on page 602

Using parameters in server behaviors

You can include parameters in a server behavior's code (see
on page 592 for more information), and let the page designer supply the necessary parameter
values before inserting the server behavior's code into the page. To let the page designer supply
parameter values, enter parameter markers within the code as shown:
@@parameterName@@
The ASP server behavior example below contains the parameter
person inserting the behavior to supply the name of a form object:
<% Session("lang_pref") = Request.Form("formParam"); %>
To create a parameter that lets the user supply the necessary value:
Enclose the
1
formParam
<% Session("lang_pref") = Request.Form("@@formParam@@"); %>
Create a dialog box that prompts the designer to supply the name of the form object.
2
For more information, see
603.
string in parameter markers:
"Creating a dialog box for a custom server behavior" on page
"Creating a dialog box for a
"Parameters in server behaviors"
, which requires the
formParam
Using parameters in server behaviors
603.
601