Specifications

Server Behaviors 175
To update the recordset name in all three positions, you need three update patterns for a single
parameter, as shown in the following example:
<updatePattern paramName="rs">
/(\b)\w+(\.CursorType)/
</updatePattern>
<updatePattern paramName="rs">
/(\b)\w+(\.CursorLocation)/
</updatePattern>
<updatePattern paramName="rs">
/(\b)\w+(\.LockType)/
</updatePattern>
Now you can pass in a new value for the recordset, and it is precisely updated in three locations.
Attribute: paramName
Description
Indicates the name of the parameter whose value is used to update the participant. This parameter
should match the ones that are specified in the insertion text and search parameters.
Parent
updatePattern
Type
Attribute.
Required
Yes.
Values
The exact name of a parameter that is used in the insertion text. For example, if the insertion text
contains an
@@rs@@, you should have a parameter with that name:
<updatePattern paramName="rs">pattern</updatePattern>
EDML Tag: delete
Description
This optional advanced feature gives control over how a participant is deleted. Without this tag,
the participant is deleted by removing it completely but only if no server behaviors refer to it. By
specifying a
<delete> tag, you can specify that it should never be deleted or that only portions
should be deleted.
Parent
implementation
Type
Tag .
Required
No.