[
https://issues.apache.org/jira/browse/SLING-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3245.
--------------------------------------
Resolution: Fixed
Fix Version/s: Tenant 1.0.2
Assignee: Felix Meschberger
Thanks for reporting and providing the patch.
Indeed we should consider all potential expressions and not abort if the first
match happens to not map to a Tenant.
Resolved in Rev. 1542627 applying the with some additional logging.
> TenantAdapterFactory can return incorrect 'null' tenants depending on order
> of pathMatchers
> -------------------------------------------------------------------------------------------
>
> Key: SLING-3245
> URL: https://issues.apache.org/jira/browse/SLING-3245
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Tenant 1.0.0
> Reporter: Vikas Saurabh
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: Tenant 1.0.2
>
> Attachments: fix_early_tenantQuery_exit.patch
>
>
> For a case where users under /home/users/abc/tenant_name/ with an existing
> tenant tenant_name (assuming pathMatchers have a correct regex to be matched)
> should be identified with correct tenant without relying on order of entries
> in pathMatchers.
> * Of course, the assumption is that pathMatchers can match a tenant name
> uniquely
> * e.g. pathMathers={"/home/users/([^/]+)/*", "/home/users/abc/([^/]+)/*}
> should work
--
This message was sent by Atlassian JIRA
(v6.1#6144)
