Save This Page
Home » » » [javadoc | source]
public class: SlingServlet [javadoc | source]

All Implemented Interfaces:
    Notifiable, Servlet, ServletConfig, Serializable

The SlingServlet is the externally visible Web Application launcher for Sling. Please refer to the full description The Sling Launchpad on the Sling Wiki for a full description of this class.

Logging goes to ServletContext.log methods.

This class goes into the secondary artifact with the classifier webapp to be used as the main servlet to be registered in the servlet container.

Method from Summary:
destroy,   getServletInfo,   init,   service,   stopped,   updated
Methods from javax.servlet.GenericServlet:
destroy,   getInitParameter,   getInitParameterNames,   getServletConfig,   getServletContext,   getServletInfo,   getServletName,   init,   init,   log,   log,   service
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from Detail:
 public  void destroy() 
    Stop the Sling framework when the web application is being stopped
 public String getServletInfo() 
 public  void init() 
    Launches the SLing framework if the sling.home setting can be derived from the configuration or the SerlvetContext. Otherwise Sling is not started yet and will be started when the first request comes in.
 public  void service(ServletRequest req,
    ServletResponse res) throws ServletException, IOException 
    If Sling has already been started, the request is forwarded to the started Sling framework. Otherwise the Sling framework is started unless there were too many startup failures.

    If the request is not forwarded to Sling, this method returns a 404/NOT FOUND if the startup failure counter has exceeded or 503/SERVICE UNAVAILABLE if the Sling framework is starting up.

    If a request causes the framework to start, it is immediately terminated with said response status and framework is started in a separate thread.

 public  void stopped() 
    The framework has been stopped by calling the Bundle.stop() on the system bundle. This actually terminates the Sling Standalone application.

    Note, that a new request coming in while the web application is still running, will actually cause Sling to restart !

 public  void updated(File updateFile) 
    The framework has been stopped with the intent to be restarted by calling either of the Bundle.update methods on the system bundle.

    If an InputStream was provided, this has been copied to a temporary file, which will be used in place of the existing launcher jar file.