[jira] Closed: (SLING-217) Scripting Resolver bundle compiled with JDK 6 may produce NoSuchMethodError

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

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

Felix Meschberger closed SLING-217.
-----------------------------------

    Resolution: Fixed

Modified the pom of the scripting/resolver project in Rev. 617428.

Using the dependency plugin the BSF 3 API is copied to a local folder and referred to in the compiler configuration to place the BSF API library in front of the standard JDK runtime library.

This seems to do the trick

> Scripting Resolver bundle compiled with JDK 6 may produce NoSuchMethodError
> ---------------------------------------------------------------------------
>
>                 Key: SLING-217
>                 URL: https://issues.apache.org/jira/browse/SLING-217
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Sometimes a NoSuchMethodError is thrown in the DefaultSlingScript.verifyBindings method when filling the javax.servlet.SimpleBindings object for the script evaluation.
> This happens, if the scripting/resolver bundle is compiled with JDK 1.6, that is the generic SimpleBindings class contained in JDK 1.6. This causes the put method to be bound to the parameters (String, Object) while the BSF 3 SimpleBindings class from the scripting/api bundle used in a JDK 1.5 environment has a put method taking (Object, Object).
> Now, one fix of course is to make sure, the scripting/resolver bundler is compiled with JDK 1.5 instead of JDK 1.6. Another solution could be to use the scripting/api bundle (or the BSF 3 library) on the boot class path for the compilation.

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