[
https://issues.apache.org/jira/browse/JCRVLT-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706079#comment-17706079
]
Julian Reschke commented on JCRVLT-700:
---------------------------------------
So it seems:
- we need more test coverage, and
- decide how to do the parsing - simply relaxing the rules in jcr-spi-commons
and jcr-commons would be a breaking change for Jackrabbit - so either we need
to copy the code and modify it (I note that there already seems to be code
duplication in PackageId), or add flags to the jcr-spi-commons APIs
Feedback appreciated.
> package creation fails for node names that are valid in Oak, but invalid in
> Jackrabbit
> --------------------------------------------------------------------------------------
>
> Key: JCRVLT-700
> URL: https://issues.apache.org/jira/browse/JCRVLT-700
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Reporter: Julian Reschke
> Priority: Major
>
> FV uses jackrabbit-spi-commons to parse node names (for instance, to get the
> namespace name and the local name). However, Jackrabbit is more strict with
> respect to non-ASCII whitespace characters than Oak.
> This leads to a situation where nodes using these characters can not be
> packaged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
