jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "ApacheSling/SlingRequestProcessing" by FelixMeschberger
Date Tue, 10 Jul 2007 14:03:57 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by FelixMeschberger:
http://wiki.apache.org/jackrabbit/ApacheSling/SlingRequestProcessing

The comment on the change is:
Fix wrong description of Content resolution

------------------------------------------------------------------------------
  
  Next the URL Mapper tries to apply prefix matching patterns. A list of patterns is iterated
checking whether the prefix applies and, if so, replacing the prefix with another prefix and
trying to resolve the result. This functionality enables relocation of a subtree of the repository.
For example, all requests whose prefix is {{{/here}}} might be remapped with the new prefix
{{{/content/there}}}. The result  of this remapping is then resolved.
  
- Resolution (currently) takes place on the last path segment of the request URL. Parts of
that segment are cut off after dots until no more dots exist in the URL. For each resulting
substring, the {{{ContentManager.load(String)}}} method is called. This processing terminates
if a {{{Content}}} object is found or if there is nothing to cut off any more.
+ Resolution (currently) takes place on the last path segment of the request URL containing
at least one dot. Parts of that segment are cut off after dots until no more dots exist in
the URL. For each resulting substring, the {{{ContentManager.load(String)}}} method is called.
This processing terminates if a {{{Content}}} object is found or if there is nothing to cut
off any more.
  
  This resolution is very simple and straight forwards. Future development may add support
for the following features:
  
-  Partial URLs:: Currently the content resolution only cuts off after dots in the last segment
of the URL path. A future enhancement might be to also cut off trailing path segements and
try to resolve the resulting paths. This will then also support the {{{ComponentRequest.getSuffix()}}}
method, which currently always returns an empty string.
   Vanity URLs:: Map the request URL according to the {{{Host}}} request header.
   Dynamic Mapping:: Add support for a set of variables in path and/or prefix mapping. For
example, a prefix mapping  may contain the string {{{/content/${lang}/${user} }}} resulting
in resolving a prefix according to the language of the current locale and the name of the
authenticated used.
  

Mime
View raw message