You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/09/06 13:54:51 UTC

[jira] [Resolved] (SLING-3042) org.apache.sling.scripting.api should not export javax.script anymore

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

Bertrand Delacretaz resolved SLING-3042.
----------------------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/r1520551 by having the scripting.api bundle just import the javax.script package, without embedding or exporting it.

All integration tests pass after this change, with JDK 1.6. This might break compatibility with JDK 1.5 but I don't think we really care about that anymore.

I have left the custom javax.script.ScriptEngineManager implementation in the bundle for now, removing it would need more analysis.
                
> org.apache.sling.scripting.api should not export javax.script anymore
> ---------------------------------------------------------------------
>
>                 Key: SLING-3042
>                 URL: https://issues.apache.org/jira/browse/SLING-3042
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting API 2.1.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Scripting API 2.1.6
>
>
> Installing the current org.apache.sling.scripting.api trunk bundle on a launchpad/testing instance causes this error:
> org.apache.sling.scripting.core.impl.ScriptEngineManagerFactory Cannot register ScriptEngineFactory org.codehaus.groovy.jsr223.GroovyScriptEngineFactory
> java.lang.ClassCastException: org.codehaus.groovy.jsr223.GroovyScriptEngineFactory cannot be cast to javax.script.ScriptEngineFactory
> And .groovy scripts are not recognized anymore, though .gsp still works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira