[
https://issues.apache.org/jira/browse/SLING-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
付尧 updated SLING-687:
---------------------
Attachment: JcrResourceResolverFactoryImpl.java.diff
I get the bug now. It is in the regex pattern of url remapping.
Sling uses _a_b to map for a:b in jcr. The pattern is this /_(.+?)_|/:
But the regex is too greedy. So, if I have this, /_a/_b, <-- Only the valid
path, no namespaces.
It will use this mapping /_(a/)_b. So the result will be /a/:b, and it is wrong.
I change the pattern to "/_([^/]+?)_|/:", only a tiny change. :)
> Can't get the resource when _ in the path
> ------------------------------------------
>
> Key: SLING-687
> URL: https://issues.apache.org/jira/browse/SLING-687
> Project: Sling
> Issue Type: Bug
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.4
> Environment: java version "1.5.0_16"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284)
> Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing)
> OS X
> Sling Launchpad app 3
> Reporter: 付尧
> Attachments: JcrResourceResolverFactoryImpl.java.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Sling can't find the resource when there is 2 " _" in the path.
> Such as /a/_b/_c.
> At that case the resource "_c" can't be found. You will get a http 404 when
> trying to get it. But you can see it in WebDAV.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
