- (TODO: breadcrumb here) +Home

Servlets

Servlets and Scripts

Servlets can be registered as OSGi services. The following service -reference properties are defined for Servlets defined as OSGi services of -type javax.servlet.Servlet:

- - - - - - - - -

Name	Description
sling.servlet.paths	A list of absolute paths under which the -servlet is accessible as a Resource. The property value must either be a -single String, an array of Strings or a Vector of Strings.
sling.servlet.resourceTypes	The resource type(s) supported by the -servlet. The property value must either be a single String, an array of -Strings or a Vector of Strings. This property is ignored if the -sling.servlet.paths property is set.
sling.servlet.selectors	The request URL selectors supported by the -servlet. The selectors must be configured as they would be specified in the -URL that is as a list of dot-separated strings such as print.a4. -The property value must either be a single String, an array of Strings or a -Vector of Strings. This property is ignored if the sling.servlet.paths -property is set.
sling.servlet.extensions	The request URL extensions supported by -the servlet for requests. The property value must either be a single -String, an array of Strings or a Vector of Strings. This property is -ignored if the sling.servlet.paths property is set.
sling.servlet.methods	The request methods supported by the servlet. -The property value must either be a single String, an array of Strings or a -Vector of Strings. This property is ignored if the sling.servlet.paths -property is set. If this property is missing, the value defaults to GET, -regardless of which methods are actually implemented/handled by the -servlet.
sling.servlet.prefix	The prefix or numeric index to make relative -paths absolute. If the value of this property is a number (int), it defines -the index of the search path entries from the resource resolver to be used -as the prefix. The defined search path is used as a prefix to mount this -servlet. The number can be -1 which always points to the last search entry. -If the specified value is higher than than the highest index of the search -paths, the last entry is used. The index starts with 0. If the value of -this property is a string and parseable as a number, the value is treated -as if it would be a number. If the value of this property is a string -starting with "/", this value is applied as a prefix, regardless of the -configured search paths! If the value is anything else, it is ignored. If -this property is not specified, it defaults to the default configuration of -the sling servlet resolver.

+ -

A SlingServletResolver listens for Servlet{}services and - given -the correct service registration properties - provides the servlets as -resources in the (virtual) resource tree. Such servlets are provided as -ServletResource instances which adapt to the javax.servlet.Servlet -class.

For a Servlet registered as an OSGi service to be used by the Sling Servlet -Resolver, the either or both of the sling.servlet.paths or the -sling.servlet.resourceTypes service reference properties must be set. -If neither is set, the Servlet service is ignored.

Each path to be used for registration - either from the -sling.servlet.paths property or constructed from the other -sling.servlet.* properties - must be absolute. Any relative path is -made absolute by prefixing it with a root path. This prefix may be set with -the sling.servlet.prefix service registration property. If this -property is not set, the first entry in the ResourceResolver search -path for the ResourceResolver.getResource(String) method is used as the -prefix. If this entry cannot be derived, a simpe slash - / - is used -as the prefix.

If sling.servlet.methods is not specified, the servlet is only -registered for handling GET requests. Make sure to list all methods you -want to be handled by this servlet.

Automated tests

The launchpad/test-services - module contains test servlets that use various combinations of the above -properties.

The launchpad/integration-tests - module contains a number of tests (like the [ExtensionServletTest|http://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/ExtensionServletTest.java] - for example) that verify the results.

Such tests run as part of our continuous integration process, to -demonstrate and verify the behavior of the various servlet registration -mechanisms, in a way that's guaranteed to be in sync with the actual Sling -core code. If you have an idea for additional tests, make sure to let us -know!

Example: Registration by Path

sling.servlet.paths = \[ "/libs/sling/sample/html", "/libs/sling/sample/txt" \]
-sling.servlet.resourceTypes = \[ "sling/unused" \]
-sling.servlet.selectors = \[ "img" \]
-sling.servlet.extensions = \[ "html", "txt", "json" \]
-

- - -

A Servlet service registered with these properties is registered under the -following paths:

/libs/sling/sample/html
/libs/sling/sample/txt

The registration properties sling.servlet.resourceTypes, -sling.servlet.selectors and sling.servlet.extensions are ignored -because the sling.servlet.paths property is set.

Example: Registration by Resource Type etc.

sling.servlet.resourceTypes = \[ "sling/unused" \]
-sling.servlet.selectors = \[ "img", "tab" \]
-sling.servlet.extensions = \[ "html", "txt", "json" \]
-

- - -

A Servlet service registered with these properties is registered under the -following paths:

{}prefix/sling/unused/img/html
{}prefix/sling/unused/img/txt
{}prefix/sling/unused/img/json
{}prefix/sling/unused/tab/html
{}prefix/sling/unused/tab/txt
{}prefix/sling/unused/tab/json

As explained the Servlet is registered for each permutation of the resource -types, selectors and extension. See above For an explanation of how -{}prefix{} is defined.

Scripts are Servlets

The Sling API defines a SlingScript interface which is used to -represent (executable) scripts inside of Sling. This interface is -implemented in the scripting/core bundle in the DefaultSlingScript -class which also implements the javax.servlet.Servlet.

To further simplify the access to scripts from the Resource tree, the -scripting/core bundle registers an AdapterFactory to adapt -Resources to Scripts and Servlets (the SlingScriptAdapterFactory). In -fact the adapter factory returns instances of the DefaultSlingScript -class for both Scripts and Servlets.

From the perspective of the Servlet resolver, scripts and servlets are -handled exactly the same. In fact, internally, Sling only handles with -Servlets, whereas scripts are packed inside a Servlet wrapping and -representing the script.

Default Servlet(s)

As explained in the Resolution Process section above, a default Servlet is -selected if no servlet (or script) for the current resource type can be -found. To make the provisioning of a default Servlet as versatile as -provisioning per resource type Servlets (or scripts), the default Servlet -is selected with just a special resource type sling/servlet/default.

The actual Servlet or Script called as the default Servlet is resolved -exactly the same way as for any resource type. That is, also for the -default Servlet selection, the request selectors and extension or method -are considered. Also, the Servlet may be a Servlet registered as an OSGi -service or it may be a Script stored in the repository or provided by any -bundle.

Finally, if not even a registered default Servlet may be resolved for the -request, because none has been registered, the servlets/resolver bundle -provides a fall back the DefaultServlet with the following -functionality:

If an NonExistingResource was created for the request the -DefaultServlet sends a 404 (Not Found)
Otherwise the DefaultServlet sends a 500 (Internal Server Error), -because normally at least a NonExistingResource should be created

OptingServlet interface

If a registered servlet implements the OptingServlet interface, Sling uses -that servlet's accepts(SlingHttpServletRequest request) method to -refine the servlet resolution process.

In this case, the servlet is only selected for processing the current -request if its accept method returns true.

Error Handler Servlet(s) or Scripts

Error handling support is now described on the Errorhandling - page.

Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. Modified: websites/staging/sling/trunk/content/sling-api.html ============================================================================== --- websites/staging/sling/trunk/content/sling-api.html (original) +++ websites/staging/sling/trunk/content/sling-api.html Sun Apr 22 17:09:56 2012 @@ -79,471 +79,10 @@

- (TODO: breadcrumb here) +Home

Sling API

The Sling API

{note:title=Work In Progress} -The contents of this page is being created at the moment. It contains -incomplete and partially wrong information as the text is adapted from the -contents of the Component API - documentation page. -{note}

Introduction

The Sling API defines a presentation framework to build Web Applications. -As such the Sling API builds upon the Servlet API but extends the latter -with new functionality:

A web page may be built from many different pieces. This aggregation of -different pieces is comparable to the functionality provided by the Portlet -API. In contrast to the latter, though, the pieces may themselves be -aggregates of yet more pieces. So a single web page response may consist of -a tree of pieces.
Just like the Servlet API and the Portlet API the Sling API mainly -defines a Java based framework. Yet the Sling API comes with the intention -of supporting scripting built.
In contrast to the Servlet API and the Portlet API, the Sling API is -resource centric. That is, the request URL does not address a servlet or a -portlet but a resource represented by an instance of the -org.apache.sling.api.resource.Resource interface. From this resource -the implementation of the Sling API will derive a javax.servlet.Servlet -or org.apache.sling.api.scripting.SlingScript instance, which is used -to handle the request.

An implementation of the presentation framework defined by the Sling API is -called a Sling Framework. The Apache Sling project actually contains two -implementations of this API: microsling and Sling. microsling (note the -lowercase m) implements the same request processing mechanisms as Sling -but is very hardcoded. It serves well as a rapid development environment as -it is quickly set up, easy to handle and shows results very easily. Sling -on the other hand is based on an OSGi framework and very flexible, allowing -the extension of the system in various ways.

Going Resource Centric

Traditional web applications are built around the notion of a traditional -application which is converted into an application which may be used using -a Web Browser. Web applications consist of a series of servlets and JSP -scripts, which are called based on configuration in the web application -deployment descriptor. Such applications are generally based on some -internal database or some static filesystem content.

The Sling API on the other hand looks more like a traditional web server -from the outside, which delivers more or less static content. Thus, while -the traditional web application uses the request URL to select a piece of -code to execute, the Sling API uses the URL to select a resource to be -delivered.

Comparsion to the Servlet API

The Sling API builds upon the Servlet API. Generally a Sling Framework will -run inside a Servlet Container and be manifested towards the Servlet -Container as a single Servlet, which dispatches requests to the Servlets -and Scripts depending on the request URLs.

Response rendering may itself be a multi-step operation. Depending on the -Servlets and Scripts, the rendering may include dispatching for child (or -even foreign) Resources.

Comparision to the Portlet API

Unlike the Portlet API, which defines one single level of portlet hierarchy -- portlets are just pieces residing besides each other - the Sling API -allows for hierarchic structuring of Resources and hence Servlet and Script -renderings. To support this structuring, the Sling Framework does not -control the rendering process of all elements on the page like the Portlet -Container does for the portlets. Instead only the Resource addressed by the -request URL is processed and it is left to the Servlet or Script rendering -that Resource to dispatch other Resource/Servlet/Script tupels to add more -data to the response.

To Iterator or To Enumeration

With the advent of the Java Collection framework in Java 2, the -Enumeration has been superceded by the Iterator. So the natural -choice for the Sling API for methods to return enumeratable collection of -objects would have be to declare the use of Iterator instances. But -because the Servlet API defines to use Enumeration instances, the Sling -API will also declare the use of Enumeration instances for consistency -with the Servlet API extended by the Sling API.

Request Processing

Unlike traditional Servlet API request processing, a Sling API request is -processed by the Sling Framework in three basic steps:

Resource Resolution - The Sling Framework derives a Resource instance -from the client request URL. The details of how to resolve the Resource. -One possible solution would be to map the request URL to a Java Content Repository - Node and return a Resource representing that Node.
Servlet and Script Resolution - From the Resource created in the first -step, the Servlet or Script is resolved based on the type of the Resource. -The resource type is a simple string, whose semantics is defined by the -Sling Framework. One possible definition could be for the resource type to -be the primary node type of the Node underlying the Resource.
Input Processing and Response Generation - After getting the Resource -and the Servlet or Script, the service() method is called or the script -is evaluated to process any user supplied input and send the response to -the client. To structure the rendered response page, this method is -responsible to include other resources. See Dispatching Requests below -for details. See Error Handling below for a discussion on how exceptions -and HTTP stati are handled.

URL decomposition

During the Resource Resolution step, the client request URL is decomposed -into the following parts:

Resource Path - The longest substring of the request URL resolving to -a Resource such that the resource path is either the complete request URL -or the next character in the request URL after the resource path is either -a dot (.) or a slash (/).
Selectors - If the first character in the request URL after the -resource path is a dot, the string after the dot upto but not including the -last dot before the next slash character or the end of the request URL. If -the resource path spans the complete request URL or if a slash follows the -resource path in the request URL, no seletors exist. If only one dot -follows the resource path before the end of the request URL or the next -slash, no selectors exist.
Extension - The string after the last dot after the resource path in -the request URL but before the end of the request URL or the next slash -after the resource path in the request URL. If a slash follows the resource -path in the request URL, the extension is empty.
Suffix Path - If the request URL contains a slash character after the -resource path and optional selectors and extension, the path starting with -the slash upto the end of the request URL is the suffix path. Otherwise, -the suffix path is empty.

Examples: Assume there is a Resource at /a/b, which has no children.

- - - - - - - - - - - - - - -

URI	Resource Path	Selectors	Extension	Suffix
/a/b	/a/b	null	null	null
/a/b.html	/a/b	null	html	null
/a/b.s1.html	/a/b	s1	html	null
/a/b.s1.s2.html	/a/b	s1.s2	html	null
/a/b/c/d	/a/b	null	null	/c/d
/a/b.html/c/d	/a/b	null	html	/c/d
/a/b.s1.html/c/d	/a/b	s1	html	/c/d
/a/b.s1.s2.html/c/d	/a/b	s1.s2	html	/c/d
/a/b/c/d.s.txt	/a/b	null	null	/c/d.s.txt
/a/b.html/c/d.s.txt	/a/b	null	html	/c/d.s.txt
/a/b.s1.html/c/d.s.txt	/a/b	s1	html	/c/d.s.txt
/a/b.s1.s2.html/c/d.s.txt	/a/b	s1.s2	html	/c/d.s.txt

+ -

{info:title=Automated tests and examples} -The SlingRequestPathInfoTest - demonstrates and tests this decomposition. Feel free to suggest additional -tests that help clarify how this works! -{info}

The SlingHttpServletRequest

The org.apache.sling.api.SlingHttpServletRequest interface defines the -basic data available from the client request to both action processing and -response rendering. The SlingHttpServletRequest extends the -javax.servlet.http.HTTPServletRequest.

This section describes the data available from the -SlingHttpServletRequest. For a complete and normative description of -the methods, refer to the Sling API JavaDoc. The following information is -represented for reference. In the case of differences between the following -descriptions and the Sling API JavaDoc, the latter takes precedence.

Resource access - Resources may be accessed from the -SlingHttpServletRequest object through the following methods: -getResource(), getResourceResolver().
Request URL information - In addition to the standard -HttpServletRequest information the SlingHttpServletRequest provides -access to the selectors, extension and suffix through the -getRequestPathInfo() method. Note that the Resource path is not -directly available form the SlingHttpServletRequest object. Instead it -is available through the Resource.getPath() method of the Resource -object retrieved through SlingHttpServletRequest.getResource().
Request Parameters - To support user input submitted as -multipart/form-data encoded POST parameters, the Sling API intrduces -the RequestParameter interface allowing file uploads. Request -parameters represented as RequestParameter objects are returned by the -following methods: getRequestParameter(String name), -getRequestParameterMap(), getRequestParameters(String name).
Request Dispatching - In addition to standard Serlvet API request -dispatching, the Sling API supports dispatching requests to render -different Resources using RequestDispatcher objects returned by the -methods: getRequestDispatcher(Resource resource) and -{{getRequestDispatcher(Resource resource, RequestDispatcherOptions -options)}}.
Miscellaneous - Finally the ComponentRequest interface provides the -following methods: getCookie(String name), -getRequestProgressTracker(), getResponseContentType(), -getResponseContentTypes(), getResourceBundle(Locale locale), -getServiceLocator().

The SlingHttpServletRequest objects are only valid during the time of -request processing. Servlets and Scripts must not keep references for later -use. As such, the SlingHttpServletRequest interface and its extensions -are defined to not be thread safe.

A note on HTTP Sessions: The SlingHttpServletRequest extends the -HttpSerlvetRequest and thus supports standard HTTP sessions. Be aware, -though that Sessions are server side sessions and hence violate the -sessionless principle of REST and therefore should be used with care. It is -almost always possible to not use sessions.

The SlingHttpServletResponse

The org.apache.sling.api.SlingHttpServletResponse interface extends the -javax.servet.http.HttpServletResponse interface and is currently empty. -It merely exists for symmetry with the SlingHttpServletRequest.

The Resource

The org.apache.sling.resource.Resource represents the data addressed by -the request URL. Resources may also be retrieved through the -org.apache.sling.api.resource.ResourceResolver. Usually this interface -is not implemented by clients. In certain use cases we call synthetic -Resource if may be usefull to define a simple object implementing the -Resource interface. The Sling Framework does not care about the -concrete implementation of the Resource interface and rather uses the -defined methods to access required information. The interface defines the -following methods:

getResourceType() - Returns the type of the resource. This resource -type is used to resolve the Servlet or Script used to handle the request -for the resource.
getPath() - Returns the path derived from the client request URL which -led to the creation of the Resource instance. See the #URL_decomposition URL decomposition - section above for more information. It is not required, that the Resource -path be a part of the original client request URL. The request URL may also -have been mapped to some internal path.
getResourceMetadata() - Returns meta data information about the -resource in a ResourceMetadata object.
adaptTo(Class type) - Returns alternative representations -of the Resource. The concrete supported classes to which the Resource may -be adapted depends on the implementation. For example a Resource based on a -JCR Node may support being adapted to the underlying Node, an -InputStream, an URL or even to a mapped object through JCR Object -Content Mapping.

The Component

The org.apache.sling.component.Component interface defines the API -implemented to actually handle requests. As such the Component interface is -comparable to the =javax.servlet.Servlet= interface. Like those other -interfaces, the Component interface provides methods for life cycle -management: init(ComponentContext context), destroy().

Processing the Request

The Component Framework calls the {{service(ComponentRequest request, -ComponentResponse response)}} method of the Component to have the component -process the request optionally processing user input, rendering the -response and optionally dispatch to other Content/Component tuples to -provide more response data.

Content and its Component

The Content object and a Component form a pair, in which the Content object -takes the passive part of providing data to the Component and the Component -takes the active part of acting upon the Content object. As a consequence, -there always exists a link between a given implementation of the Content -interface and a given implementation of the Component interface.

This link is manifested by the Component identifier available from the -Content object through the Content.getComponentId() method on the one -hand. On the other hand, the link is manifested by the -getContentClassName() and createContentInstance() methods of the -Component interface.

Component Lifecylce

When a Component instance is created and added to the Component framework, -the init(ComponentContext) method is called to prepare and initialize -the Component. If this method terminates abnormally by throwing an -exception, the Component is not used. The Component Framework -implementation may try at a later time to recreate the Component, intialize -it and use it. If the Component Framework tries to recreate the Component a -new instance of the Component must be created to be initialized and used.

When the Component has successfully been initialized, it may be referred to -by Content objects. When a client request is to be processed, the Content -object is resolved and the service method on the Component to which the -Content object refers is called. The service method may - and generally -will - be called simultaneously to handle different requests in different -threads. As such, implementations of these methods must be thread safe.

When the Component Framework decides to take a Component out of service, -the destroy() method is called to give the Component a chance to -cleanup any held resources. The destroy method must only be called by the -Component Framework when no more request processing is using the Component, -that is no thread may be in the service method of a Component to be -destroyed. Irrespective of whether the destroy method terminated normally -or abnormally, the Component will not be used again.

The addition and removal of Components is at the discretion of the -Component Framework. A Component may be loaded at framework start time or -on demand and my be removed at any time. But only one single Component -instance with the same Component identifier may be active at the same time -within a single Component Framework instance.

The ComponentExtension

To enhance the core functionality of Components, each Component may have -zero, one ore more Component Extensions attached. A Component Extensions is -a Java object implementing the -org.apache.sling.component.ComponentExtension interface. This interface -just defines a getName() method to identify extensions.

The concrete implementation as well as instantiation and management of -Component Extensions is left to the Component Framework implementation with -one restriction though: The extensions must be available to the Component -at the time the init(ComponentContext) method is called may only be -dropped after the destroy() method terminates.

The Component interface defines two methods to access Extensions: The -getExtensions() method returns a java.util.Enumeration of all -ComponentExtension objects attached to the component. If no Component -Extension are attached to the Component, an empty enumeration is returned. -The getExtension(String name) returns the named Component Extension -attached to the Component or null if no such Component Extension is -attached to the Component.

Component Frameworks are allowed to share Component Extension instances of -the same name between different Component instances. Regardless of whether -Component Extensions are shared or not, they must be thread safe, as any -Component Extension may be used within the service method, which -themselves may be called concurrently.

Request Processing Filters

Similar to the Servlet API providing filters for filtering requests and/or -responses the Component API provides the -org.apache.sling.component.ComponentFilter interface. The filters are -called by a ComponentFilterChain and either handle the request, -manipulate the request and/or response object and finally forward the -request and response optionally wrapped to the -ComponentFilterChain.doFilter(ComponentRequest, ComponentResponse) -method.

Like the Components filters have a defined lifecycle manifested by -init and destroy methods. When the filter enters the system, the -Component Framework calls the ComponentFilter.init(ComponentContext) -method. Only when this method completes successfully will the filter be put -into action and be used during request processing. When the filter leaves -the system, the Component Framework removes the filter from being used in -filter chains and calls the ComponentFilter.destroy() method. This -method is not expected to throw any exceptions. The filter may be removed -from the Component Framework at the discretion of the Component Framework -or because the filter is being unregistered from the Component Framework by -some means outside this specification.

This specification does not define how ComponentFilter objects are -registered with the Component Framework nor is it specified how the order -in which the filters are called is defined. Likewise it is outside this -specification how the filter instances registered with the Component -Framework are configured.

Sessions

The org.apache.sling.component.ComponentSession interface provides a -way to identify a user across more than one request and to store transient -information about that user.

A component can bind an object attribute into a ComponentSession by -name. The ComponentSession interface defines two scopes for storing -objects: APPLICATION_SCOPE, COMPONENT_SCOPE. All objects stored in -the session using the APPLICATION_SCOPE must be available to all the -components, servlets and JSPs that belong to the same component application -and that handle a request identified as being a part of the same session. -Objects stored in the session using the COMPONENT_SCOPE must be -available to the component during requests for the same content that the -objects where stored from. Attributes stored in the COMPONENT_SCOPE are -not protected from other web components of the component application. They -are just conveniently namespaced.

The component session extends the Servlet API HttpSession. Therefore -all HttpSession listeners do apply to the component session and -attributes set in the component session are visible in the HttpSession -and vice versa.

The attribute accessor methods without the scope parameter always refer -to COMPONENT_SCOPE attributes. To access APPLICATION_SCOPE -attributes use the accessors taking an explicit scope parameter.

A final note on Sessions: Sessions are server side sessions and hence -violate the sessionless principle of REST and therefore should be used with -care. It is almost always possible to not use sessions.

Dispatching Requests

To include renderings of child Content objects, a -org.apache.sling.component.ComponentRequestDispatcher object may be -retrieved from the ComponentContext with which the Component has been -initialized or from the ComponentRequest provided to the service method. -Using this dispatcher the reponse of rendering the Content may be included -by calling the {{ComponentRequestDispatcher.include(ComponentRequest, -ComponentResponse)}} method.

This method is comparable to the -RequestDispatcher.include(ServletRequest, ServletResponse method of the -Servlet API but dispatching by the ComponentRequestDispatcher does not -go through the servlet container and stays within the Component Framework.

The service method of included Components are called with an instance -of the ComponentRequest interface whose getContent() returns the -Content object for the included Content.

When a Component is included by another component the following request -attributes are set:

- - - - -

Request Attributes	Type	Description
org.apache.sling.component.request.content	String	The Content -instance to which the client URL resolved. This attribute is set when -included Components are being rendered and it is not set for the Component -directly addressed by the client request.
org.apache.sling.component.request.component	String	The -Component instance for the Content object to which the client URL -resolved. This attribute is set when included Components are being rendered -and it is not set for the Component directly addressed by the client -request.

- -

Error Handling

While processing requests, the service methods called may have -problems. Components have multiple options of reporting issues during -processing to the client:

Set the status of the HTTP response calling the -ComponentResponse.setStatus method
Send an error page calling the ComponentResponse.sendError method
Throw an exception

If such an exception is thrown, the Component Framework must act upon the -exception in one of the following ways:

If the request is processed through Servlet API request inclusion, the -exception must be given back to the servlet container. A -ComponentException is just forwarded as a ServletException. This is -a requirement of the Servlet API specification which states for included -requests:

{quote}

Otherwise, the Component Framework may handle the error itself in a -manner similar to the error handling approach defined the Servlet API -specification (Section SRV 9.9 Error Handling of the Java Servlet -Specification 2.4). Specifically the request attributes defined by the -Servlet API specification must be set for the error handler:

- - - - - - - - - -* If the Component Framework decides to not handle the error itself, the -exception must be forwarded to the servlet container as a -*ComponentException* wrapping the original exception as its root cause. -

Request Attributes	Type	Description
javax.servlet.error.status_code	java.lang.Integer	The status -code of the response. In the case of an exception thrown from the -service, the code is defined by the Component Framework.
javax.servlet.error.exception_type	java.lang.Class	The fully -qualified name of the exception class thrown. This attribute does not -exist, if error handling does not result from an exception. This attribute -is maintained for backwards compatibility according to the Servlet API -Specification.
javax.servlet.error.message	java.lang.String	The message of -the exception thrown. This attribute does not exist, if error handling does -not result from an exception. This attribute is maintained for backwards -compatibility according to the Servlet API Specification.
javax.servlet.error.exception	java.lang.Throwable	The -exception thrown. This attribute does not exist, if error handling does not -result from an exception.
javax.servlet.error.request_uri	java.lang.String	The request -URL whose processing resulted in the error.
javax.servlet.error.servlet_name	java.lang.String	The name of -the servlet which yielded the error. The servlet name will generally not -have any significance inside the Component Framework.
org.apache.sling.component.error.componentId	java.lang.String	-The identifier of the Component whose service method has caused the -error. This attribute does not exist, if the Component Framework itself -caused the error processing.

- -

This specification does not define, how error handlers are configured and -used if the Component Framework provides error handling support. Likewise -the Component Framework may or may not implement support to handle calls to -the ComponentResponse.sendError method. The Component Framework may -also use its own error handling also for errors resulting from request -processing failures, for example if authentication is required or if the -request URL cannot be resolved to a Content object.

Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. Modified: websites/staging/sling/trunk/content/sling-testing-tools.html ============================================================================== --- websites/staging/sling/trunk/content/sling-testing-tools.html (original) +++ websites/staging/sling/trunk/content/sling-testing-tools.html Sun Apr 22 17:09:56 2012 @@ -79,183 +79,10 @@

- (TODO: breadcrumb here) -

Sling Testing Tools

Sling provides a number of testing tools to support the following use -cases: - Run JUnit tests contributed by OSGi bundles in an OSGi system. This does -not require Sling and should work in other OSGi environments. - Run scriptable tests in a Sling instance, using any supported scripting -language. -* Run integration tests via HTTP against a Sling instance that is started -during the Maven build cycle, or independently.

This page describes those tools, and points to the bundles that implement -them.

The testing/samples/integration-tests - module demonstrates these tools, and is also meant as a sample project to -show how to run integration tests for Sling-based applications.

The main Sling integration tests at launchpad/integration-tests - were created before this testing framework, and do not use it yet (as of -March 2011). The new testing tools are simpler to use, but the "old" tests -(all 400 of them as I write this) fulfill their validation role for testing -Sling itself, there's no real need to modify them to use the new tools.

Server-side JUnit tests contributed by bundles

The services provided by the org.apache.sling.junit.core - bundle allow bundles to register JUnit tests, which are executed -server-side by the JUnitServlet registered by default at -/system/sling/junit. This bundle is not dependent on Sling, it should -work in other OSGi environments.

{warning:title=JUnit servlet security} -Note that the JUnitServlet does not require authentication, so it would -allow any client to run tests. The servlet can be disabled by configuration -if needed, but in general the /system path should not be accessible to -website visitors anyway. -{warning}

{note:title=SlingJUnitServlet} -For tighter integration with Sling, the alternate SlingJUnitServlet is -registered with the sling/junit/testing resource type and .junit -selector, if the bundle is running in a Sling system. Using this servlet -instead of the plain JUnitServlet also allows Sling authentication to be -used for running the tests, and the standard Sling request processing is -used, including servlet filters for example. -{note}

To try the JUnitServlet interactively, install the org.apache.sling.testing.samples.sampletests - bundle.

This bundle contains a number of test classes, which are registered with -the org.apache.sling.junit.core services by way of the -Sling-Test-Regexp=.Test bundle header, defined in the bundle's -pom.xml*. The JUnit core services use this regular expression to select -which classes of the test bundle should be executed as JUnit tests.

To list the available tests, open http://localhost:8080/system/sling/junit/ -. The servlet shows available tests, and allows you to execute them via a -POST request.

Adding a path allows you to select a specific subset of tests, as in -http://localhost:8080/system/sling/junit/org.apache.sling.junit.remote.html -- the example integration tests described below use this to selectively -execute server-side tests. The JUnitServlet provides various output -formats, including in particular JSON, see -http://localhost:8080/system/sling/junit/.json for example.

To supply tests from your own bundles, simply export the tests classes and -add the Sling-Test-Regexp header to the bundle so that the Sling JUnit -core services register them as tests.

Injection of OSGi services

The @TestReference annotation is used to inject OSGi services in tests -that are executed server side.The BundleContext can also be injected in -this way, see the OsgiAwareTest - for an example.

Curl examples

Here's an example executing a few tests using curl:

Running tests with curl

- $ curl -X POST -http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.sampletests.JUnit.json - [{ - "INFO_TYPE": "test", - "description": -"testPasses(org.apache.sling.testing.samples.sampletests.JUnit3Test)" - },{ - "INFO_TYPE": "test", - "description": -"testPasses(org.apache.sling.testing.samples.sampletests.JUnit4Test)" - },{ - "INFO_TYPE": "test", - "description": -"testRequiresBefore(org.apache.sling.testing.samples.sampletests.JUnit4Test)" - } - ]

And another example with a test that fails: -

Failing tests with curl

- $ curl -X POST -http://localhost:8080/system/sling/junit/org.apache.sling.testing.samples.failingtests.JUnit4FailingTest.json - [continuous integration|SLINGxSITE:Project Information]

Scriptable server-side tests

If the org.apache.sling.junit.scriptable - bundle is active in a Sling system, (in addition to the -org.apache.sling.junit.core bundle), scriptable tests can be executed -by the JUnitServlet according to the following rules:

A node that has the sling:Test mixin is a scriptable test node.
For security reasons, scriptable test nodes are only executed as tests if -they are found under /libs or /apps, or more precisely under a path -that's part of Sling's ResourceResolver search path.
To execute a test, the scriptable tests provider makes an HTTP requests -to the test node's path, with a .test.txt selector and extension, and -expects the output to contain only the string TEST_PASSED. Empty lines -and comment lines starting with a hash sign (#) are ignored in the output, -and other lines are reported as failures.

The ScriptableTestsTest - class, from the integration test samples module described below, sets up -such a test node and its accompanying script, and calls the JUnitServlet to -execute the test. It can be used as a detailed example of how this works.

Integration tests example

The testing/samples/integration-tests - module runs some simple integration tests against a Sling Launchpad -instance that's setup from scratch before running the tests.

This module's pom and Java code can be used as examples to setup your own -integration testing modules for Sling-based apps - or for any other -runnable jar that provides an http service.

Besides serving as examples, some of the tests in this module are used to -validate the testing tools. They run as part of the full Sling continuous integration - build, so they're guaranteed to be correct examples if that build is -successful.

The sample uses the testing/tools - to make the test code simpler. See the [OsgiConsoleTest|https://svn.apache.org/repos/asf/sling/trunk/testing/samples/integration-tests/src/test/java/org/apache/sling/testing/samples/integrationtests/http/OsgiConsoleTest.java] - class for an example of a test that's very readable and requires no test -setup or boilerplate code.

The following steps are executed in the integration-test phase of this -module's Maven build: -1. A random port number for the Sling server is selected by the Maven build -helper plugin, unless explicitely set (see pom.xml for such options). -1. Additional bundles, defined in the module's pom, are downloaded from the -Maven repository in the target/sling/additional-bundles folder. -1. The first test that inherits from the SlingTestBase - class causes the Sling runnable jar (defined as a dependency in the -module's pom) to be started. -1. # The SlingTestBase class waits for the Sling server to be ready, -based on URLs and expected responses defined in the pom. -1. # The SlingTestBase class installs and starts the bundles found in the -target/sling/additional-bundles folder. -1. The test can now either test Sling directly via its http interface, or -use the JUnitServlet to execute server-side tests contributed by bundles or -scripts, as described above. -1. The Sling runnable jar is stopped when the test VM exits. -1. The test results are reported via the usual Maven mechanisms.

If -DkeepJarRunning is used on the Maven command line, the Sling -runnable jar does not exit, to allow for running individual tests against -this instance, for example when debugging the tests or the server code. See -the pom for details.

Remote test execution

The testing tools support two types of remote test execution.

SlingRemoteTestRunner

The SlingRemoteTestRunner - is used to run tests using the JUnitServlet described above. In this -case, the client-side JUnit test only defines which tests to run and some -optional assertions. Checking the number of tests executed, for example, -can be useful to make sure all test bundles have been activated as -expected, to avoid ignoring missing test bundles.

See the ServerSideSampleTest - class for an example.

SlingRemoteExecutionRule

The SlingRemoteExecutionRule - is a JUnit Rule that allows tests to be executed remotely in a Sling -instance from an IDE, assuming the test is available on both sides.

The ExampleRemoteTest - class demonstrates this. To run it from your IDE, set the -sling.remote.test.url in the IDE to the URL of the JUnitServlet, like -http://localhost:8080/system/sling/junit for example.

+Home

+ +

Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. Modified: websites/staging/sling/trunk/content/sling.html ============================================================================== --- websites/staging/sling/trunk/content/sling.html (original) +++ websites/staging/sling/trunk/content/sling.html Sun Apr 22 17:09:56 2012 @@ -79,390 +79,10 @@

- (TODO: breadcrumb here) +Home

Sling

Maven Sling Plugin

The Maven Sling Plugin provides a number of goals which may be of help -while developping bundles for Sling. To run the plugin you need at least -Maven 2.x and JDK 1.5 or higher. Maven Sling Plugin provides the following -goals:

- - - + - - -

[sling:deploy](#deploy.html) -	Deploy a OSGi-bundle into a running Sling instance.
[sling:deploy-file](#deploy-file.html) -	Deploy a OSGi-bundle into a running Sling instance without requiring a -project descriptor file.
[sling:install-file](#install-file.html) -	Install a OSGi-bundle into a running Sling instance without requiring a -project descriptor file.

- -

Usage

You should specify the version in your project's plugin configuration:

<project>
-  ...
-  <build>
-    <!-- To define the plugin version in your parent POM -->
-    <pluginManagement>
-      <plugins>
-    <plugin>
-      <groupId>org.apache.sling</groupId>
-      <artifactId>maven-sling-plugin</artifactId>
-      <version>2.0.5-SNAPSHOT</version>
-    </plugin>
-    ...
-      </plugins>
-    </pluginManagement>
-    <!-- To use the plugin goals in your POM or parent POM -->
-    <plugins>
-      <plugin>
-    <groupId>org.apache.sling</groupId>
-    <artifactId>maven-sling-plugin</artifactId>
-    <version>2.0.5-SNAPSHOT</version>
-      </plugin>
-      ...
-    </plugins>
-  </build>
-  ...
-</project>
-

- - -

For more information, see "Guide to Configuring Plug-ins"

{anchor:deploy}

The deploy goal

The deploy goal uploads a bundle to a Sling OSGi Bundle Repository -server implemented by the sling-obr bundle, which may be located on a -remote system. The plugin places an HTTP POST request to the server -sending the bundle file.

Use

To use the deploy goal of the Maven Sling Plugin define the following -elements in the section of the POM:

<?xml version="1.0" encoding="ISO-8859-1"?>
-<project>
-  ....
-  <build>
-    ....
-    <plugins>
-      ....
-      <plugin>
-    <groupId>org.apache.sling</groupId>
-    <artifactId>maven-sling-plugin</artifactId>
-    <executions>
-      <execution>
-        <id>deploy-bundle</id>
-        <goals>
-          <goal>deploy</goal>
-        </goals>
-      </execution>
-    </executions>
-      </plugin>
-      ....
-    <plugins>
-    ....
-  <build>
-  ....
-<project>
-

- - -

Configuration

The deploy goal may be configured in the element -using the following properties: - - - - - - -{anchor:deploy-file} -
Parameter Default Value System Property Overwrite Description -
skip false sling.deploy.skip Whether to skip this step -even though it has been configured in the project to be executed. The main -use of this setting is preventing deployment of the bundle to a Sling OSGi -Bundle Repository server if it is known that there is none or if such an -upload is not required.
buildDirectory ${project.build.directory} - The path of -the file to be installed
jarName ${project.build.finalName}.jar - The name of the -file to be installed
obr - obr The URL of the running Sling instance to which -the bundle is installed. Note that this parameter is required and has no -defualt value. It must always be specified in the configuration section or -on the command line.

Parameter	Default Value	System Property Overwrite	Description -
skip	false	sling.deploy.skip	Whether to skip this step -even though it has been configured in the project to be executed. The main -use of this setting is preventing deployment of the bundle to a Sling OSGi -Bundle Repository server if it is known that there is none or if such an -upload is not required.
buildDirectory	${project.build.directory}	-	The path of -the file to be installed
jarName	${project.build.finalName}.jar	-	The name of the -file to be installed
obr	-	obr	The URL of the running Sling instance to which -the bundle is installed. Note that this parameter is required and has no -defualt value. It must always be specified in the configuration section or -on the command line.

The deploy-file goal

The deploy-file goal is equivalent to the deploy goal except, that -the deploy-file does not require a project descriptor file while the -deploy goal does. In other words the deploy-file goal may used to -upload any bundle file available to a Sling OBR server instance.

Use

The deploy-file goal may only be used from the command line by -explicitly calling it as in:

$ mvn org.apache.sling:maven-sling-plugin:deploy-file -Dsling.file=<file>
-

- - -

-Dobr=

Specifying the bundle file to upload with the sling.file property is -required.

Configuration

The deploy-file supports similar configuration parameters as the -deploy goal with the exception of the skip parameter which makes no -sense. In addition, all parameters must be specified on the command line by -setting system properties. The bundleFileName parameter specified as -the sling.file system property as well as the obr URL are required -by the deploy-file goal. - - - - -Example: To deploy the bundle file someBundle.jar to the OBR running at {{http://obr.sample.org -}} you might use the goal as follows:
-
$ mvn org.apache.sling:maven-sling-plugin:deploy-file -
- - -
-Dsling.file=someBundle.jar -Dobr=http://obr.sample.org
-
{anchor:install}
-
-
The install goal
-
The install goal uploads a bundle to a running sling instance, which -may be located on a remote system. The plugin places an HTTP POST -request to the sling instance sending the bundle file together with flags -indicating whether to start the bundle and what start level to assign the -bundle. It's also possible to HTTP PUT instead of POST for WebDAV.
-
-
Use
-
To use the install goal of the Maven Sling Plugin define the following -elements in the section of the POM:
-
<?xml version="1.0" encoding="ISO-8859-1"?> -<project> - .... - <build> - .... - <plugins> - .... - <plugin> - <groupId>org.apache.sling</groupId> - <artifactId>maven-sling-plugin</artifactId> - <executions> - <execution> - <id>install-bundle</id> - <goals> - <goal>install</goal> - </goals> - </execution> - </executions> - </plugin> - .... - <plugins> - .... - <build> - .... -<project> -
- - -
-
Configuration
-
The install goal may be configured in the element -using the following properties: -
Parameter Default Value System Property Overwrite Description -
bundleFileName -${project.build.directory}/${project.build.finalName}.jar -sling.file The path and name of the file to be installed
obr - obr The URL of the running Sling instance to which -the bundle is installed. Note that this parameter is required and has no -defualt value. It must always be specified in the configuration section or -on the command line.
- - - - - - - -
- - - - -
{anchor:install-file} -
Parameter Default Value System Property Overwrite Description -
skip false sling.install.skip Whether to skip this step -even though it has been configured in the project to be executed. The main -use of this setting is preventing installation of the bundle to a running -Sling installation if it is known that there is none or if such an upload -is not required, for example when building the bundle in an automated build -system such as Confluence.
bundleFileName -${project.build.directory}/${project.build.finalName}.jar -sling.file The path and name of the file to be installed
bundleStart true sling.bundle.start Whether to start -the bundle after installing it. If the bundle is just updated, this -parameter is ignored even if the bundle is currently stopped
bundleStartLevel 20 sling.bundle.startlevel The start -level to set on the installed bundle. If the bundle is already installed -and therefore is only updated this parameter is ignored. The parameter is -also ignored if the running Sling instance has no StartLevel service (which -is unusual actually)
slingUrl http{}://localhost:8080/sling sling.url -The URL of the running Sling instance to which the bundle is installed
user admin sling.user The name of the user to -authenticate as with the running Sling instance given by the slingUrl -parameter
password admin sling.password The password of the user -to authenticate as with the running Sling instance given by the -slingUrl parameter
*usePut* *false* *sling.usePut* If a simple HTTP PUT should -be used instead of the standard POST to the felix console. In the -uninstall goal, a HTTP DELETE will be used.
*refreshPackages* *true* *sling.refreshPackages* Whether to refresh the packages after installing the uploaded bundle. If this property is set to *true*, the {{PackageAdmin.refreshPackages(Bundle\[\](\.html) -)}} method is called after installing or updating the bundle.

Parameter	Default Value	System Property Overwrite	Description -
bundleFileName	-${project.build.directory}/${project.build.finalName}.jar	-sling.file	The path and name of the file to be installed
obr	-	obr	The URL of the running Sling instance to which -the bundle is installed. Note that this parameter is required and has no -defualt value. It must always be specified in the configuration section or -on the command line.

Parameter	Default Value	System Property Overwrite	Description -
skip	false	sling.install.skip	Whether to skip this step -even though it has been configured in the project to be executed. The main -use of this setting is preventing installation of the bundle to a running -Sling installation if it is known that there is none or if such an upload -is not required, for example when building the bundle in an automated build -system such as Confluence.
bundleFileName	-${project.build.directory}/${project.build.finalName}.jar	-sling.file	The path and name of the file to be installed
bundleStart	true	sling.bundle.start	Whether to start -the bundle after installing it. If the bundle is just updated, this -parameter is ignored even if the bundle is currently stopped
bundleStartLevel	20	sling.bundle.startlevel	The start -level to set on the installed bundle. If the bundle is already installed -and therefore is only updated this parameter is ignored. The parameter is -also ignored if the running Sling instance has no StartLevel service (which -is unusual actually)
slingUrl	http{}://localhost:8080/sling	sling.url	-The URL of the running Sling instance to which the bundle is installed
user	admin	sling.user	The name of the user to -authenticate as with the running Sling instance given by the slingUrl -parameter
password	admin	sling.password	The password of the user -to authenticate as with the running Sling instance given by the -slingUrl parameter
usePut	false	sling.usePut	If a simple HTTP PUT should -be used instead of the standard POST to the felix console. In the -uninstall goal, a HTTP DELETE will be used.
refreshPackages	true	sling.refreshPackages	Whether to refresh the packages after installing the uploaded bundle. If this property is set to true, the {{PackageAdmin.refreshPackages(Bundle\[\](\.html) -)}} method is called after installing or updating the bundle.

The install-file goal

The install-file goal is equivalent to the install goal except, -that the install-file does not require a project descriptor file while -the install goal does. In other words the install-file goal may -used to upload any bundle file available to a running Sling instance.

Use

The install-file goal may only be used from the command line by -explicitly calling it as in:

$ mvn org.apache.sling:maven-sling-plugin:install-file -Dsling.file=<file>
-

- - -

Specifying the bundle file to upload with the sling.file property is -required.

Configuration

The install-file supports the same configuration parameters as the -install goal with the exception of the skip parameter which makes -no sense. In addition, all parameters must be specified on the command line -by setting system properties. The bundleFileName parameter specified as -the sling.file system property is required by the install-file -goal.

For a description of the parameters see the configuration section of the install goal - above.

Example: To upload the bundle file someBundle.jar you might use the -goal as follows:

$ mvn org.apache.sling:maven-sling-plugin:install-file
-

- - -

-Dsling.file=someBundle.jar

{anchor:uninstall}

The uninstall goal

The uninstall goal uninstalls a bundle from a running sling instance, -which may be located on a remote system. The plugin uninstalles a bundle -via a HTTP POST{}request. It's also possible to use HTTP DELETE -instead of POST for WebDAV.

Use

To use the uninstall goal of the Maven Sling Plugin define the -following elements in the section of the POM:

<?xml version="1.0" encoding="ISO-8859-1"?>
-<project>
-  ....
-  <build>
-    ....
-    <plugins>
-      ....
-      <plugin>
-    <groupId>org.apache.sling</groupId>
-    <artifactId>maven-sling-plugin</artifactId>
-    <executions>
-      <execution>
-        <id>uninstall-bundle</id>
-        <goals>
-          <goal>uninstall</goal>
-        </goals>
-      </execution>
-    </executions>
-      </plugin>
-      ....
-    <plugins>
-    ....
-  <build>
-  ....
-<project>
-

- - -

Configuration

The uninstall goal may be configured in the element -using the following properties: - - - - - - - -{anchor:validate} -
Parameter Default Value System Property Overwrite Description -
bundleFileName -${project.build.directory}/${project.build.finalName}.jar -sling.file The path and name of the file to be uninstalled
slingUrl http{}://localhost:8080/sling sling.url -The URL of the running Sling instance to which the bundle should be -uninstalled
user admin sling.user The name of the user to -authenticate as with the running Sling instance given by the slingUrl -parameter
password admin sling.password The password of the user -to authenticate as with the running Sling instance given by the -slingUrl parameter
usePut false sling.usePut In the uninstall goal, a HTTP -DELETE will be used.

Parameter	Default Value	System Property Overwrite	Description -
bundleFileName	-${project.build.directory}/${project.build.finalName}.jar	-sling.file	The path and name of the file to be uninstalled
slingUrl	http{}://localhost:8080/sling	sling.url	-The URL of the running Sling instance to which the bundle should be -uninstalled
user	admin	sling.user	The name of the user to -authenticate as with the running Sling instance given by the slingUrl -parameter
password	admin	sling.password	The password of the user -to authenticate as with the running Sling instance given by the -slingUrl parameter
usePut	false	sling.usePut	In the uninstall goal, a HTTP -DELETE will be used.

The validate goal

The validate goal checks the JSON code of a bundle.

Use

To use the validate goal of the Maven Sling Plugin define the following -elements in the section of the POM:

<?xml version="1.0" encoding="ISO-8859-1"?>
-<project>
-  ....
-  <build>
-    ....
-    <plugins>
-      ....
-      <plugin>
-    <groupId>org.apache.sling</groupId>
-    <artifactId>maven-sling-plugin</artifactId>
-    <executions>
-      <execution>
-        <id>validate-bundle</id>
-        <goals>
-          <goal>validate</goal>
-        </goals>
-      </execution>
-    </executions>
-      </plugin>
-      ....
-    <plugins>
-    ....
-  <build>
-  ....
-<project>
-

- - -

Configuration

The validate goal may be configured in the element -using the following properties: - - - -
-
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. Modified: websites/staging/sling/trunk/content/the-sling-engine.html ============================================================================== --- websites/staging/sling/trunk/content/the-sling-engine.html (original) +++ websites/staging/sling/trunk/content/the-sling-engine.html Sun Apr 22 17:09:56 2012 @@ -79,43 +79,10 @@

- (TODO: breadcrumb here) -
-
The Sling Engine
-
-
-
The Sling Engine
-
-
General
-
-
Architecture
-
Authentication
-
-
-
Request Handling
-
-
Dispatching Requests
-
URL decomposition
-
Request Listeners
-
Filters
-
Servlets and Scripts
-
Errorhandling
-
Request Parameters
-
-
-
Resources
-
-
Resources
-
Wrap or Decorate Resources
-
Mappings for Resource Resolution
-
-
-
Misc
-
-
Adapters
-
Eventing and Jobs
-
+Home
+ +
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Parameter Default Value System Property Overwrite Description -
skip false sling.validation.skip Whether to skip the -validation
skipJson false sling.validation.skipJson Whether to -skip the JSON validation. At the time, there's no difference between -skip and skipJson because only JSON files will be validated by now. -

Name	Description
sling.servlet.paths	A list of absolute paths under which the -servlet is accessible as a Resource. The property value must either be a -single String, an array of Strings or a Vector of Strings.
sling.servlet.resourceTypes	The resource type(s) supported by the -servlet. The property value must either be a single String, an array of -Strings or a Vector of Strings. This property is ignored if the -sling.servlet.paths property is set.
sling.servlet.selectors	The request URL selectors supported by the -servlet. The selectors must be configured as they would be specified in the -URL that is as a list of dot-separated strings such as print.a4. -The property value must either be a single String, an array of Strings or a -Vector of Strings. This property is ignored if the sling.servlet.paths -property is set.
sling.servlet.extensions	The request URL extensions supported by -the servlet for requests. The property value must either be a single -String, an array of Strings or a Vector of Strings. This property is -ignored if the sling.servlet.paths property is set.
sling.servlet.methods	The request methods supported by the servlet. -The property value must either be a single String, an array of Strings or a -Vector of Strings. This property is ignored if the sling.servlet.paths -property is set. If this property is missing, the value defaults to GET, -regardless of which methods are actually implemented/handled by the -servlet.
sling.servlet.prefix	The prefix or numeric index to make relative -paths absolute. If the value of this property is a number (int), it defines -the index of the search path entries from the resource resolver to be used -as the prefix. The defined search path is used as a prefix to mount this -servlet. The number can be -1 which always points to the last search entry. -If the specified value is higher than than the highest index of the search -paths, the last entry is used. The index starts with 0. If the value of -this property is a string and parseable as a number, the value is treated -as if it would be a number. If the value of this property is a string -starting with "/", this value is applied as a prefix, regardless of the -configured search paths! If the value is anything else, it is ignored. If -this property is not specified, it defaults to the default configuration of -the sling servlet resolver.

Request Attributes	Type	Description
org.apache.sling.component.request.content	String	The Content -instance to which the client URL resolved. This attribute is set when -included Components are being rendered and it is not set for the Component -directly addressed by the client request.
org.apache.sling.component.request.component	String	The -Component instance for the Content object to which the client URL -resolved. This attribute is set when included Components are being rendered -and it is not set for the Component directly addressed by the client -request.

Request Attributes	Type	Description
javax.servlet.error.status_code	java.lang.Integer	The status -code of the response. In the case of an exception thrown from the -service, the code is defined by the Component Framework.
javax.servlet.error.exception_type	java.lang.Class	The fully -qualified name of the exception class thrown. This attribute does not -exist, if error handling does not result from an exception. This attribute -is maintained for backwards compatibility according to the Servlet API -Specification.
javax.servlet.error.message	java.lang.String	The message of -the exception thrown. This attribute does not exist, if error handling does -not result from an exception. This attribute is maintained for backwards -compatibility according to the Servlet API Specification.
javax.servlet.error.exception	java.lang.Throwable	The -exception thrown. This attribute does not exist, if error handling does not -result from an exception.
javax.servlet.error.request_uri	java.lang.String	The request -URL whose processing resulted in the error.
javax.servlet.error.servlet_name	java.lang.String	The name of -the servlet which yielded the error. The servlet name will generally not -have any significance inside the Component Framework.
org.apache.sling.component.error.componentId	java.lang.String	-The identifier of the Component whose service method has caused the -error. This attribute does not exist, if the Component Framework itself -caused the error processing.

Parameter	Default Value	System Property Overwrite	Description -
skip	false	sling.validation.skip	Whether to skip the -validation
skipJson	false	sling.validation.skipJson	Whether to -skip the JSON validation. At the time, there's no difference between -skip and skipJson because only JSON files will be validated by now. -

Servlets

Servlets and Scripts

Automated tests

Example: Registration by Path

Example: Registration by Resource Type etc.

Scripts are Servlets

Default Servlet(s)

OptingServlet interface

Error Handler Servlet(s) or Scripts

Sling API

The Sling API

Introduction

Going Resource Centric

Comparsion to the Servlet API

Comparision to the Portlet API

To Iterator or To Enumeration

Request Processing

URL decomposition

The SlingHttpServletRequest

The SlingHttpServletResponse

The Resource

The Component

Processing the Request

Content and its Component

Component Lifecylce

The ComponentExtension

Request Processing Filters

Sessions

Dispatching Requests

Error Handling

Sling Testing Tools

Sling Testing Tools

Server-side JUnit tests contributed by bundles

Injection of OSGi services

Curl examples

Scriptable server-side tests

Integration tests example

Remote test execution

SlingRemoteTestRunner

SlingRemoteExecutionRule

Sling

Maven Sling Plugin

Usage

The deploy goal

Use

Configuration

The deploy-file goal

Use

Configuration

The install goal

Use

Configuration

The install-file goal

Use

Configuration

The uninstall goal

Use

Configuration

The validate goal

Use

Configuration

The Sling Engine

The Sling Engine

General

Request Handling

Resources

Misc