[
https://issues.apache.org/jira/browse/JCR-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515617
]
angela commented on JCR-996:
----------------------------
apart from discussing the interfaces, we may take a look at the implications of
Path/Name interfaces.
I could see the followings issues that we need to get a consensus about:
- Would it be an option to change the derived interfaces in
jackrabbit-jcr-commons in order to use the Name/Path
interfaces instead of QName/Path classes. I think of
- NamespaceResolver
- NameCache
- PathCache
- The same question arises for
- NameFormat
- PathFormat
Since both the 'core' and the various modules in the spi contrib make use of
the mentioned functionality present in jackrabbit-jcr-commons, i think this
issue should be discussed on a broader basis.
Copying the utilities to the SPI-commons just in order to be able the change
them doesn't seem a sensible solution to me.
> Name and Path interfaces in SPI
> -------------------------------
>
> Key: JCR-996
> URL: https://issues.apache.org/jira/browse/JCR-996
> Project: Jackrabbit
> Issue Type: Improvement
> Components: SPI
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Attachments: JCR_996_spi.patch
>
>
> The SPI interface currently has a dependency to QName and Path classes in
> jackrabbit-jcr-commons. Architecturally it would be better to have Name and
> Path interfaces in the SPI package, and have the implementing classes in
> commons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
