[jira] [Created] (JEXL-192) Invalid return type when expected rsult is null

["Constantin Mitocaru (JIRA)" <ji...@apache.org>]

Constantin Mitocaru created JEXL-192:
----------------------------------------

             Summary: Invalid return type when expected rsult is null
                 Key: JEXL-192
                 URL: https://issues.apache.org/jira/browse/JEXL-192
             Project: Commons JEXL
          Issue Type: Bug
    Affects Versions: 3.0
            Reporter: Constantin Mitocaru
            Priority: Blocker


In jexl2 this code correctly outputs the line:

{code}
null
{code}

{code:java}
        JexlEngine jexl = new JexlEngine();
        Record r = new Record();
        r.setHeader(new RecordHeader());
        JexlContext jc = new MapContext();
        jc.set("r", r );
        jc.set("com.s.objects.record.RecordUtils", com.s.objects.record.RecordUtils.class );
        Expression e = jexl.createExpression( "com.s.objects.record.RecordUtils.getHeaderAgeOrResolveItFromDOB(r)" );
        System.out.println( e.evaluate(jc) );        
{code}

The signature of the method getHeaderAgeOrResolveItFromDOB() is:

{code:java}
        public static Integer getHeaderAgeOrResolveItFromDOB( final Record rec ) {
        ...
        }
{code}

But in jexl3 this code produces:

{code}
	class com.s.objects.record.RecordUtils
{code}


{code:java}
        JexlEngine jexl = new JexlBuilder().create();
        Record r = new Record();
        r.setHeader(new RecordHeader());
        JexlContext jc = new MapContext();
        jc.set("r", r );
        jc.set("com.s.objects.record.RecordUtils", com.s.objects.record.RecordUtils.class );
        JexlExpression e = jexl.createExpression( "com.s.objects.record.RecordUtils.getHeaderAgeOrResolveItFromDOB(r)" );
        System.out.println( e.evaluate(jc) );        
{code}

So it returns the class of the utility rather than the value null!

I think jexl3 version 3.0 was not really ready for prime time.
I really screwed up my project upgrading to 3.0.
When do you guys anticipate to release 3.1?
Is there a way to work with a snapshot after this fix?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)