-
-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unsetScriptEngineFactory method throws exception on OH shutdown #3521
Comments
Which script engines did you install? Only DSL? |
I just saw this on my systems running build 3392. I have |
@jimtng While this code is removed in #3487, the new code is similar. It seems that some script engine factories (I don't no which one) seem to report an empty list for supported script types, when the factory is disposed. This will also lead to an empty preferred extension and the corresponding transformation service is not deactivated, but they'll no longer work. Maybe we should use the factory itself as key in the list of created transformation services, WDYT? |
As I said, it was a 'bare' install. So it has (or has not) whatever script engines get installed by default. |
I did encounter an empty extension. Unless the factory changed its answer about scriptTypes during its lifetime, it won't be added in the first place, because it's checked during service creation
@J-N-K I guess this might be the safer way to go |
Even an empty extension should not happen (although it might be the factory only reports MIME-types). But in this case it means that |
IIRC, it was reported by |
Yes, I figured that out a minute ago. I'm wondering why we have that at all, all scripting add-ons inherit from |
On shutdown a 'bare' OH SNAPSHOT throws an exception
The unsetScriptEngineFactory method has thrown an exception java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
-- it looks like the shutdown code fails because there are no rules defined.The text was updated successfully, but these errors were encountered: