[
https://issues.apache.org/jira/browse/JEXL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739201#action_12739201
]
Sebb commented on JEXL-70:
--------------------------
I've already coded something along the lines I suggested, but that has revealed
a slight problem:
the script engine factory requires the bsf-api jar or Java 1.6, which is not
ideal.
I think there probably need to be two classes, one for script engine use, and
the other for direct Jexl calls, but I'm not sure the more versatile SCXML
approach is needed.
> 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.
