Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <811280338.1249991895292.JavaMail.jira@brutus>
Date: Tue, 11 Aug 2009 04:58:15 -0700 (PDT)
From: "Sebb (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (JEXL-70) Add main class to allow scripts etc to
 be tested
In-Reply-To: <1366311504.1249420814925.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JEXL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741822#action_12741822 ] 

Sebb commented on JEXL-70:
--------------------------

Two new Main classes have been added:

jexl.scripting.Main
jexl.Main

which test JSR-223 and plain Jexl respectively.

These are very basic at present, and need enhancing.

> 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.