Rahul Akolkar wrote:
>
> ...
> Correct, some patterns of usage make more sense than others. But to
> make any claims via the 223 API, we have to do rigorous code
> inspection and add some tests. Until someone does that, lets return
> null.
> ...
>
Should I create a bug for later then - just as a reminder ?
I can add some multi-threaded tests but I'm not sure they'll "prove"
multi-threading; they could only prove something if they were to fail. :-)
And about the ScriptContext (at least the engine & global bindings) , I
guess we'd need to alter those to be synchronized & thread safe.
Aren't there any guidelines in the spec (or even tests via the TCK) or
something that could serve as a base ?
--
View this message in context:
http://www.nabble.com/-JEXL--2.0-JSR-223-initial-implementation-added---what-next--tp24750307p24772036.html
Sent from the Commons - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
