You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/11/25 12:42:39 UTC

[jira] Resolved: (SLING-190) The Sling class of the launcher should verify minimum JDK requirement and fail properly

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

Felix Meschberger resolved SLING-190.
-------------------------------------

    Resolution: Won't Fix

I think we can close this issue as "won't fix" because there is probably no real value in it (any longer).

> The Sling class of the launcher should verify minimum JDK requirement and fail properly
> ---------------------------------------------------------------------------------------
>
>                 Key: SLING-190
>                 URL: https://issues.apache.org/jira/browse/SLING-190
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: 3
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> Currently, there is no check for the minimum Java Runtime environment required by Sling so, Sling will just fail with nasty exceptions if the requirement is not met. The Sling launcher (standalone app and web app) should be modified to fail gently in such cases:
>    * The launcher is built agains JDK 1.4
>    * The launcher checks for the required runtime version
>    * If the runtime version is not correct, Sling should be terminated:
>           -> standalone should just write the message to stderr and terminate the VM
>           -> web app should log a message to the servlet container and throw a permanent UnavailableException

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