You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by fm...@apache.org on 2014/01/31 09:21:26 UTC

svn commit: r1563082 - /sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

Author: fmeschbe
Date: Fri Jan 31 08:21:26 2014
New Revision: 1563082

URL: http://svn.apache.org/r1563082
Log:
Fix type (thanks Reza Jalili for reporting)

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext?rev=1563082&r1=1563081&r2=1563082&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/mappings-for-resource-resolution.mdtext Fri Jan 31 08:21:26 2014
@@ -1,6 +1,5 @@
 Title: Mappings for Resource Resolution
 
-
 ## Configuration
 
 
@@ -29,7 +28,7 @@ Note, that these node types only help se
 
 ## Namespace Mangling
 
-There are systems accessing Sling, which have a hard time handling URLs containing colons – `:` – in the path part correctly. Since URLs produced and supported by Sling may colons because JCR Item based resources may be namespaced (e.g. `jcr:content`), a special namespace mangling feature is built into the `ResourceResolver.resolve` and `ResourceResolver(map)` methods.
+There are systems accessing Sling, which have a hard time handling URLs containing colons – `:` – in the path part correctly. Since URLs produced and supported by Sling may contain colons because JCR Item based resources may be namespaced (e.g. `jcr:content`), a special namespace mangling feature is built into the `ResourceResolver.resolve` and `ResourceResolver(map)` methods.
 
 Namespace mangling operates such, that any namespace prefix identified in resource path to be mapped as an URL in the `map` methods is modified such that the prefix is enclosed in underscores and the colon removed.