jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2098) SPI layer should only pass through supported repository descriptors
Date Wed, 06 May 2009 07:36:30 GMT

    [ https://issues.apache.org/jira/browse/JCR-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706328#action_12706328

angela commented on JCR-2098:

the SPI layer should pass through all the descriptors and the implementation is in charge
of returning only the descriptors that are really supported.

in contrast: the JCR2SPI layer MUST be able to deal with all functionality and options that
can occur with a specific version of the JCR API.

Having the JCR2SPI layer filter out some descriptors is from my point of view a mistake. what
is required instead is that JCR2SPI gets adjusted to fit all the new features/options of JCR
The suggested fix just works around that lack and I find it only acceptable as a temporary
solution. Jukka, could you mark the corresponding code accordingly?

Regarding this issue: I don't think this is really an improvement and would like to have the
corresponding code removed before the release thus making this issue invalid.


> SPI layer should only pass through supported repository descriptors
> -------------------------------------------------------------------
>                 Key: JCR-2098
>                 URL: https://issues.apache.org/jira/browse/JCR-2098
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi, jackrabbit-spi2jcr
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
> As we add new the JCR 2.0 conformance tests to jcr-tests (see JCR-208) there will be
spi2jcr test failures as the SPI layer has not been updated to support all these new features.
The SPI layer should reflect that by only passing through those repository descriptors that
it can support.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message