[
https://issues.apache.org/jira/browse/SLING-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847838#comment-16847838
]
Eric Norman commented on SLING-7764:
------------------------------------
Closing this without including the changes in any official release.
This issue and solution has become obsolete due to the work done for SLING-8418
The migration path from the SLING-7764 solution to the SLING-8418 solution
would be something like:
{quote}a) Change the custom bundle that contained the custom_index.html file to
no longer be a fragment bundle attached to the org.apache.sling.starter.startup
artifact that no longer exists. The fragment can become a regular non-fragment
bundle or the custom_index.html file can be moved somewhere else and get rid of
the fragment bundle entirely.
b) Modify the
org.apache.felix.hc.core.impl.filter.ServiceUnavailableFilter-startupandshutdown
service configuration to provide the alternate path to the custom page. For
example, in the starter project (or a fork of it), change the
responseTextFor503 value in the
org-apache-sling-starter/src/main/provisioning/healthcheck.txt file.{quote}
> The starting up page content should be customizable
> ---------------------------------------------------
>
> Key: SLING-7764
> URL: https://issues.apache.org/jira/browse/SLING-7764
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Starter Startup 1.0.6
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Minor
> Fix For: Starter Startup 1.0.8
>
>
> To enable branding and more site specific information in the starting up
> page, the startup filter should support providing a custom page provided via
> a bundle fragment.
> This should work basically the same way as the customizable form login page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
