[
https://issues.apache.org/jira/browse/JCR-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-3535:
--------------------------------
Attachment: path-test.log
With the recent changes, the integration tests path with both settings.
However, this is because the client side now sends absolute paths (instead of
absolute URIs), when it can.
An "old" client (or a non Jackrabbit-client) might however still send absolute
URIs. The server needs to be able to deal with this as well.
The attached log files shows the failures for the integration tests when the
server is configured for absolute paths, but the client still uses full URIs.
> Davex remoting should support absolute path hrefs
> -------------------------------------------------
>
> Key: JCR-3535
> URL: https://issues.apache.org/jira/browse/JCR-3535
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-spi2dav
> Affects Versions: 2.6
> Reporter: Timothee Maret
> Assignee: Julian Reschke
> Attachments: failure-diff.txt, JCR-3535.1.patch, JCR-3535.2.patch,
> path-test.log
>
>
> JCR-1873 introduced an optional support for hrefs as absolute paths (instead
> of URIs).
> This feature should also be supported by the Davex remoting (client side).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira