[
https://issues.apache.org/jira/browse/OAK-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412921#comment-13412921
]
Julian Reschke commented on OAK-66:
-----------------------------------
Today I tried two approaches, which in the end turned out to be a BIG mess:
1) Copy over the relevant code from jcr2spi and spicommons; replacing all
instances of Name and Path by String. Trouble is; these are really many
classes, and it's not clear that hacking them this way will be useful.
2) Try to refactor SPI to make everything that uses Name and Path to use
Generics. This looked promising first, but again got messy really quick.
Tomorrow I'll try something else to make progress: in OAK-JCR; simply implement
Name and Path as wrappers around Strings containing Oak names and paths. This
will add additional objects, but might be the best way to get something up and
running quickly without duplicating tons of code.
> JCR Node Type Management
> ------------------------
>
> Key: OAK-66
> URL: https://issues.apache.org/jira/browse/OAK-66
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core, jcr
> Reporter: angela
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
