commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: [JEXL] Multi-statement expression evaluation - change to last?
Date Wed, 14 May 2008 00:53:58 GMT
On 5/13/08, sebb <sebbaz@gmail.com> wrote:
> On 13/05/2008, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
>  > On 5/13/08, sebb <sebbaz@gmail.com> wrote:
<snip/>
>  >  >  However, the result of the expression is currently taken to be the
>  >  >  first statement.
>  >  >
>  >  >  This is at odds with other scripting languages such as Javascript and
>  >  >  Beanshell which return the value of the last statement.
>  >  >
>  >
>  > <snip/>
>  >
>  >  You can get that behavior using oacj.Script rather than
>  >  oacj.Expression. Perhaps you are looking for scripts?
>
>
> I'm using the BSF interface, which has either Object eval() or void
>  exec() methods.
>
>  This is for use in JMeter, which needs the returned Object.
>
>  I'd not realised that the Script method returned an Object - I've just
>  changed the JexlEngine code I took from JEXL-39 to use that instead
>  and that has fixed it for JMeter.
>
>  However, what to do for the official Jexl-BSF implementation?
>
>  Seems to me that it would be best to use Script for that as well; it
>  will still be usable with a single expression.
>
<snap/>

Yup, makes sense. I'll add a pointer to this thread in JEXL-39.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message