[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649420#action_12649420
]
Vidar S. Ramdal commented on SLING-249:
---------------------------------------
@Bertrand
I'm not sure about caching domainRoots. At least in our case, we need to add
domains run-time. So at least we need a simple way to re-scan the domain info.
Thinking about it, a query like //*[contains(sling:domains,
request.getHeader("Host"))] allows domain roots to be located all over the
tree, at any level. We might not want domain roots located under other domain
roots. Maybe we should specify that domain roots must be located directly under
jcr:root (or another specified location) - in which case the query should be
something like /*[contains(sling:domains, request.getHeader("Host"))]
> 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.
