[ 
https://issues.apache.org/jira/browse/STANBOL-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292785#comment-13292785
 ] 

Rupert Westenthaler commented on STANBOL-608:
---------------------------------------------

While working on that I discovered that the switch to SLING launchpad 2.4.0 
will require the addition of the 

    javax.activation,
    javax.jws.**,
    javax.transaction.**,
    javax.xml.**,
    org.w3c.dom.**,
    org.xml.sax.**

to the Stanbol framework fragment as those are no longer included in the JRE 
properties of the SLING (compare [1] and [2])

if someone has a better solution please comment.

[1] 
http://svn.apache.org/repos/asf/sling/tags/org.apache.sling.launchpad.base-2.3.0/src/main/resources/jre-1.6.properties
[2] 
http://svn.apache.org/repos/asf/sling/trunk/launchpad/base/src/main/resources/jre-1.6.properties
 
                
> Stanbol is incompatible with Java 7
> -----------------------------------
>
>                 Key: STANBOL-608
>                 URL: https://issues.apache.org/jira/browse/STANBOL-608
>             Project: Stanbol
>          Issue Type: Bug
>    Affects Versions: 0.9.0-incubating
>         Environment: java version 1.7.*
>            Reporter: Rupert Westenthaler
>              Labels: java7
>
> launching the Stanbol launcher under Java 7 fails with the follwing Exception
>     10.05.2012 06:40:50.133 *ERROR* [main] Failed to Start OSGi framework
>     org.osgi.framework.BundleException: Uncaught Instantiation Issue:
>     java.lang.ArrayIndexOutOfBoundsException: -1
>            at 
> org.apache.sling.launchpad.base.impl.Sling.<init>(Sling.java:245)
> This is caused by Stanbol using an outdated SLING lauchpad base module that 
> does not support Java 7. (see 
> https://issues.apache.org/jira/browse/SLING-2281)
> To fix this we need to upgrade to version 2.4.0.
> Thx to Andreas Kuckartz for reporting [1]!
> [1] http://markmail.org/message/paqchtf32gubt64y
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to