commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JEXL-70) Add main class to allow scripts etc to be tested
Date Tue, 04 Aug 2009 21:36:14 GMT

     [ https://issues.apache.org/jira/browse/JEXL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rahul Akolkar updated JEXL-70:
------------------------------

    Fix Version/s: Later

Sounds good, testing scripts as well as a command line interactive approach are both of value
I think.

Rather than one main class, if you're interested in doing this, I'd suggest looking at doing
something like the Commons SCXML test package:

  http://svn.apache.org/repos/asf/commons/proper/scxml/branches/J6/src/main/java/org/apache/commons/scxml/test/

This will allow for building various flavors of testers or interactive helpers.

Setting fix version to Later (i.e. whenever patches become available).


> Add main class to allow scripts etc to be tested
> ------------------------------------------------
>
>                 Key: JEXL-70
>                 URL: https://issues.apache.org/jira/browse/JEXL-70
>             Project: Commons JEXL
>          Issue Type: New Feature
>            Reporter: Sebb
>            Priority: Minor
>             Fix For: Later
>
>
> I think it would be useful to include a main() class which could be used to test scripts.
> Something very simple, just one optional parameter which is the name of the script file.
> If omitted, then read expressions from System.in.
> The app would evaluate the script/expression and print the return value.
> If the JexlEngine is created using JexlScriptEngineFactory, then it would allow easy
testing of the JSR-223 features (i.e. JEXL object) as well.
> WDYT?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message