JcrResourceResolver2 incorrectly loads existing configuration into its map
entries
----------------------------------------------------------------------------------
Key: SLING-750
URL: https://issues.apache.org/jira/browse/SLING-750
Project: Sling
Issue Type: Bug
Components: JCR Resource
Affects Versions: JCR Resource 2.0.4
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: JCR Resource 2.0.4
After the implementation of SLING-249 the new JcrResourceResolver2 class is
expected to read existing JcrResourceResolverFactory configuration into its
internal map entry list. This has a series of problems though:
* The .*/.*/ pattern to match any scheme and any host is too greedy. The
pattern should be [^/]+/[^/]+/ to not swallow slashes
* Virtual Host entries were treated as prefix matches. They should rather be
defined as hooked patterns using the ^ and $ charaters
* URL Mapping entries were added the wrong way around, such that instead of
mapping /* to /content/* etc. the mapping was /content/* to /* etc.
* Multiple replacement of matched URL parts with replacement failed due to
wrong java.util.Matcher use
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
