[
https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592880#action_12592880
]
Felix Meschberger commented on SLING-190:
-----------------------------------------
The launcher is self-contained with respect to other Sling modules. It just
uses "itself", the Felix framework as well as the OSGi API modules. The Felix
framework and the OSGi API modules are built as JDK 1.3 class files.
The Sling launcher would be built as 1.4 class files without any use of JDK 5
features. I once had a prototype, but somehow lost it along the ways :-(
I suggest we simply deschedule this issue from the initial release leaving it
to be implemented later.
> 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: Launcher
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> 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.
