To follow up my own message: I've updated the ldap client search code to detect if a search returns any results or not, and updated the sampler to generate different codes for success (200), no results (201), and failure (500). User-defined searches work OK for me, but YMMV.
More work is needed to improve the error codes and messages, and to look at what should go in the requestData and responseData fields, but hopefully there is enough information to be able to use the sampler and response assertions in some real tests. Please be aware that the result codes may need to change. Unfortunately, the Gump builds are not working at present, because of an error in a pre-requisite build. I've reported the bug, but in the meantime, if anyone cannot build from CVS and wants a compiled version, please let me know off-list, and I can see about sending you a copy. S. -----Original Message----- From: BAZLEY, Sebastian Sent: 12 November 2003 16:59 To: JMeter Developers List Subject: LDAP suggestions: It looks as though the SampleResult fields are not being utilised fully by the LDAP code. It seems to me that the response code could be used to distinguish various kinds of success - for example, using HTTP-style values: 2xx - search succeeded, some results found 2yy - search succeeded, no results found 4xx - some kind of error 5xx - another kind of error I leave it to others more familiar with LDAP as to what exact form the error codes should take (and what the corresponding messages should be), but I think this approach would fit in with the rest of JMeter, and would allow the use of a Response Assertion to convert a search with no results into a failed sample. == The other area where the sample result could be better used is the response Data. This is currently set to "success full" - but does not appear in the Tree View, because the DataType is not being set to TEXT. The sampler could have another field to specify which attributes to return. [Is there a sensible default set of attributes that applies to all/most LDAP implementations? I don't know.] == If these suggestions make sense, I am happy to help with updating the code in CVS. -- Sebastian Bazley --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
