Author: cziegeler
Date: Fri Jul 17 08:33:59 2009
New Revision: 795008
URL: http://svn.apache.org/viewvc?rev=795008&view=rev
Log:
Clean up javadocs
Modified:
sling/trunk/bundles/api/src/main/java/org/apache/sling/api/scripting/SlingScriptResolver.java
Modified:
sling/trunk/bundles/api/src/main/java/org/apache/sling/api/scripting/SlingScriptResolver.java
URL:
http://svn.apache.org/viewvc/sling/trunk/bundles/api/src/main/java/org/apache/sling/api/scripting/SlingScriptResolver.java?rev=795008&r1=795007&r2=795008&view=diff
==============================================================================
---
sling/trunk/bundles/api/src/main/java/org/apache/sling/api/scripting/SlingScriptResolver.java
(original)
+++
sling/trunk/bundles/api/src/main/java/org/apache/sling/api/scripting/SlingScriptResolver.java
Fri Jul 17 08:33:59 2009
@@ -22,33 +22,16 @@
* The <code>ScriptResolver</code> interface defines the API for a service
* capable of locating scripts. Where the script is actually located is an
* implementation detail of the service implementation.
- * <p>
- * Find scripts in the repository, based on the current Resource type. The
- * script filename is built using the current HTTP request method name,
followed
- * by the extension of the current request and the desired script extension.
For
- * example, a "js" script for a GET request on a Resource of type some/type
with
- * request extension "html" should be stored as
- *
- * <pre>
- * /sling/scripts/some/type/get.html.js
- * </pre>
- *
- * in the repository.
- * <p>
- * Applications of the Sling Framework generally do not need the servlet
- * resolver as resolution of the servlets to process requests and sub-requests
- * through a <code>RequestDispatcher</code> is handled by the Sling Framework.
- * <p>
*/
public interface SlingScriptResolver {
/**
- * Finds the given name to a {...@link SlingScript}.
+ * Finds the {...@link SlingScript} for the given name.
* <p>
* The semantic meaning of the name is implementation specific: It may be
an
* absolute path to a <code>Resource</code> providing the script source or
* it may be a relative path resolved according to some path settings.
- * Finally, the name may also just be used as an itentifier to find the
+ * Finally, the name may also just be used as an identifier to find the
* script in some registry.
*
* @param resourceResolver The <code>ResourceResolver</code> used to
