[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650789#action_12650789
]
Felix Meschberger commented on SLING-249:
-----------------------------------------
In Rev. 720647 I implemented a first shot at a new JCR ResourceResolver called
JcrResourceResolver2. In addition I added configuration to the
JcrResourceResovlerFactoryImpl to select the new (default) or old resource
resolver. This selection may also be made by setting the
"resource.resolver.new" framework property (e.g. in sling.properties) to true
(use new resolver) or false (use old resolver).
This property and its corresponding configuration option is temporary and will
be removed again as soon as the new resource resovler is acceptable and the old
resource resolver is dropped.
For more information on this new resource resolver, refer to the wiki page at
http://cwiki.apache.org/SLING/flexible-resource-resolution.html
> Allow mapping nodes to internet domains
> ---------------------------------------
>
> Key: SLING-249
> URL: https://issues.apache.org/jira/browse/SLING-249
> Project: Sling
> Issue Type: New Feature
> Components: Engine
> Affects Versions: JCR Resource 2.0.2
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> Sling should support hosting multiple domains, with different JCR roots.
> E.g.:
> http://www.domain1.com could map to /content/domain1.com
> http://www.domain2.com could map to /content/domain2.com
> While developing a website, the fully qualified domain might not be
> available. Ideally, the mapping could be configured in a flexible way. One
> option would be to maintain a set of regular expressions to match against
> URLs. Each regexp would then match to a path in the JCR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
