JIRA issue and attach the patch(es) to that.
Patches to mailing lists may get overlooked - or lost, as has
apparently happened here
On 07/10/2008, Vishal Goenka <[EMAIL PROTECTED]> wrote:
> Please find a patch for the ASTBlock statement bug. I will follow up with
> jUnit test case as wel
:38 PM
To: Commons Developers List; [EMAIL PROTECTED]
Subject: Re: [JEXL] - 1.1.1 release?
On Thu, Sep 11, 2008 at 1:00 PM, Vishal Goenka <[EMAIL PROTECTED]> wrote:
> I have been using JEXL 1.1.1-SNAPSHOT for a few months now in a production
> environment to leverage the array and
I have been using JEXL 1.1.1-SNAPSHOT for a few months now in a production
environment to leverage the array and map support. Except for two issues
that I sent out to the mailing list (see below) things are working great for
me and I was wondering if a 1.1.1 release may be in the offing anytime soo
Say I declare a function:
public void fn(String s1, Object [] s2);
This function is then added to a JEXL context and referenced in an
expression thus:
fn('hello', ['a', 'b', 'c']);
This invokes the function with the argument ['a', 'b', 'c'] wrapped in
another array.
Thus, s2[0] == ['a', 'b'
The ExpressionFactory throws an exception when parsing a block statement
such as:
{ a='b'; c='d'; }
I traced it down to a missing check for ASTBlock in the ExpressionFactory.
The patch is attached although it was generated against a local checkin of
this file in my local svn, hence version
