You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Róbert Csákány (JIRA)" <ji...@apache.org> on 2009/12/10 16:14:18 UTC
[jira] Commented: (SLING-1198) Allow mapping nodes to internet
domains with template parameters
[ https://issues.apache.org/jira/browse/SLING-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788740#action_12788740 ]
Róbert Csákány commented on SLING-1198:
---------------------------------------
Jonathan,
I've implemented another patch where you can define @noparam@ in mappings - for example to use for shared contents by several domains, but there is a major conceptional issue. If you use parameters, you have to use all of them, or none of them, because the reversebility. In @noparam@ type mappings there are no reverse mapping - how can you determinate subdomain, if there will be severeal - thats the problem is presented also when you miss one or more parameters.
I attach the modified patch - but as Felix described his DRAFT (http://cwiki.apache.org/confluence/display/SLING/Resource+Resolution+Plugins), I will investigate to make my path "pluggable", because I have another type of mapping requirements in my projects.
> Allow mapping nodes to internet domains with template parameters
> ----------------------------------------------------------------
>
> Key: SLING-1198
> URL: https://issues.apache.org/jira/browse/SLING-1198
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Affects Versions: JCR Resource 2.0.2
> Reporter: Róbert Csákány
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
> Attachments: MapEntry.patch
>
>
> 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.