Extensions to JMeter

We have made the following custom extensions to JMeter:

Support for “Equals” response assertion. This support also required an extension to make search results stable (that is, ordered alphabetically by search DN and attribute id) so that the Equals tests make sense. However, when more search results are returned than the limit configured using ldapsampler.max_sorted_results=2000 in jmeter-home/bin/jmeter.properties, sorting is disabled.
Variable From File Controller was added, so that the contents of a named file can now be read into a specified JMeter variable for use in later test steps.
JMeter was modified to allow multiple attribute values to be specified in a modify request through the following XML semantics.
A JMeter modify request can take the following as a modification value:
```
<list><value>value1</value><value>value2</value><value>value3</value></list>
```

The following symbolic strings were introduced so that they can be used instead of their cryptic numeric forms:

LDAP Extended Request: Search Test: “Scope” Field (scope for LDAP search operation)

String in JMeter Test	Numeric Equivalent	Java Constant (in javax.naming.directory.SearchControls)
object	0	OBJECT_SCOPE
onelevel	1	ONELEVEL_SCOPE
subtree	2	SUBTREE_SCOPE

LDAP Extended Request: Modification Test: “opCode” Column (mode for LDAP MODIFY operation)

String in JMeter Test	Numeric Equivalent	Java Constant (in javax.naming.directory.DirContext)
add	1	ADD_ATTRIBUTE
replace	2	REPLACE_ATTRIBUTE
remove	3	REMOVE_ATTRIBUTE