[SLING-750] JcrResourceResolver2 incorrectly loads existing configuration into its map entries

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.4
• Fix Version/s: JCR Resource 2.0.4
• Component/s: JCR
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 02/Dec/08 13:25
• Updated: 13/Sep/09 13:22
• Resolved: 14/Dec/08 20:52

Description

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