On 19 May 2015 at 00:35, Nigel Donaldson <[email protected]> wrote:
> Hello Flavio, and thanks for responding.
>
> In a number of cases, I use a short list of arguments to BeanShell scripts.
> However, some of my scripts have to work with many tens of (extracted
> run-time) variables, so a long tail of variables passed-in as arguments is
> (IMO, impracticably) unwieldy.
In that case, if you want run-time evaluation of the variable, use code like
vars.get("VAR1")
rather than
${VAR1}
> Nige
>
>
>> -----Original Message-----
>> From: Flavio Cysne [mailto:[email protected]]
>> Sent: Monday, 18 May 2015 10:31 PM
>> To: JMeter Users List
>> Subject: Re: Loop controller behaviour
>>
>> I didn't see before that there is an error message referring to a
>> BeanShell
>> sampler in JMeter's log sent in the first message. If you are using
>> expressions
>> like this "field_${Fields_g1}" inside your BeanShell code, I advise you to
>> pass
>> variables, or expressions using variables, as arguments (i.e. don't use
>> JMeter
>> variables or functions inside BeanShell code, or prefer not to) to avoid
>> interpreter exception during execution. BeanShell code is compiled to a
>> "static" version (if "Reset before each call" is not checked).
>>
>> I built a script similar to which you presented, but ATM I'm not seeing
>> errors
>> or unexpected behaviors. I'll try to post it and send the link into this
>> thread.
>
> ---------------------------------------------------------------------
> 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]
