jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-191) ChangeExtractor uses interfaces from oak.spi.state
Date Fri, 12 Oct 2012 16:47:02 GMT

    [ https://issues.apache.org/jira/browse/OAK-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475143#comment-13475143
] 

Michael Dürig commented on OAK-191:
-----------------------------------

I suggest to move {{ChangeExtractor}} from package {{api}} to {{spi/observation}}, remove
its accessor from {{Root}} and make the observation manager into a plugin. That is, move package
{{jcr/observation}} to {{plugins/observation}}.
                
> ChangeExtractor uses interfaces from oak.spi.state
> --------------------------------------------------
>
>                 Key: OAK-191
>                 URL: https://issues.apache.org/jira/browse/OAK-191
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>
> from my understanding the oak-api should not rely on interfaces/classes
> defined by the oak.spi package space.
> while looking at the different Tree implementations and the usage of
> NodeState (defined in the spi) i realized that the ChangeExtractor makes in
> fact use of the org.apache.jackrabbit.oak.spi.state.NodeStateDiff which in
> turn has a dependency to NodeState from the same package. That way the
> NodeState interface gets exposed with the oak-api which looks a rather
> awkward to me.
> i think this should be reconsidered. and maybe we also have to take
> a second look at the distinction between oak-api and oak-spi.

--
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

Mime
View raw message