Okay, I have managed to make it work. The problem was the Recording Controller that was the parent of the HTTP Requests. I included it in the original post just in case it was relevant and it turns out that it was. It existed because I originally recorded the script using the proxy. Now that I am manipulating the script by hand I have moved the requests out of the Recording Controller and the regex functions now work.
Thanks for your help Mike. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au > From: Scott Eade <[EMAIL PROTECTED]> > Reply-To: "JMeter Users List" <[EMAIL PROTECTED]> > Date: Thu, 12 Dec 2002 20:05:59 +1100 > To: JMeter Users List <[EMAIL PROTECTED]> > Subject: Re: regexFunction > > Nah, I mistyped it in the email message. > > I have been using the Function Helper Dialog with the same result. > > Any other suggestions? > > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > >> From: "Mike Stover" <[EMAIL PROTECTED]> >> Reply-To: "JMeter Users List" <[EMAIL PROTECTED]> >> Date: Thu, 12 Dec 2002 03:48:35 -0500 >> To: JMeter Users List <[EMAIL PROTECTED]> >> Subject: Re: regexpFunction >> >> Could it be that you are using "__regexpFunction" when the name is actually >> "__regexFunction"? (ie, no 'p'). At first, I thought it was just a typo in >> your email, >> but I noticed you did it twice.... >> >> Using the Function Dialog Helper would avoid such problems too. >> >> -Mike >> >> On 12 Dec 2002 at 16:56, Scott Eade wrote: >> >>> I can't for the life of me get a regexp function to work. Here is what I >>> have set up: >>> >>> JMeter version: cvs head >>> JDK: 1.4.0_01 >>> >>> Test Plan >>> Thread Group >>> Recording Controller >>> HTTP Request 1: Output includes numerous anchor elements >>> HTTP Request 2 (POST): Sends a parameter thus: >>> Name: parm1 >>> Value: ${__regexpFunction(<a href=(.*)>,$1$,1,,,)} >>> Encode: No >>> >>> This is a contrived example based on Mike's original posting of the regexp >>> functionality, the real expression I would like to execute is quite >>> different. My problem is that I cannot get this to work - the result is >>> always empty (i.e. The query data always shows "parm1=" rather than >>> "parm1=_some_value_found_by_the_regexp_function_"). >>> >>> Any assistance you can provide with making this work would be greatly >>> appreciated. >>> >>> Cheers, >>> >>> Scott >>> -- >>> Scott Eade >>> Backstage Technologies Pty. Ltd. >>> http://www.backstagetech.com.au >>> >>> >>> >>> -- >>> To unsubscribe, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> For additional commands, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> >> >> >> >> -- >> Michael Stover >> [EMAIL PROTECTED] >> Yahoo IM: mstover_ya >> ICQ: 152975688 >> AIM: mstover777 >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
