[jira] Resolved: (BSF-30) ScriptEngineManager swallows Exception when iterating factories

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

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

Sebb resolved BSF-30.
---------------------

    Resolution: Fixed

AFAICT, the behaviour of the BSF version of ScriptEngineManager does not violate the API, so closing as fixed.

> ScriptEngineManager swallows Exception when iterating factories
> ---------------------------------------------------------------
>
>                 Key: BSF-30
>                 URL: https://issues.apache.org/jira/browse/BSF-30
>             Project: BSF
>          Issue Type: Bug
>          Components: BSF-3.x
>    Affects Versions: BSF-3.0
>            Reporter: Sebb
>
> ScriptEngineManager swallows Exception when iterating factories.
> This is not ideal - it should certainly not swallow ThreadDeath for example.
> Unfortunately the Javadoc for ServiceRegistry.lookupProviders() only specifies that it may generate an Error.
> Note that the version of ScriptEngineManager in Sun Java 1.6 does not swallow Exception.
> This leads to different behaviour when using bsf-engines on Java 1.5 and 1.6.
> On 1.5, the BSF version of ScriptEngineManager is used - this continues to process factories after an Error has occured.
> However, on Java 1.6, the first error terminates the class constructor so the manager is not available to create any engines at all.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org