jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-996) Name and Path interfaces in SPI
Date Thu, 11 Oct 2007 16:58:50 GMT

     [ https://issues.apache.org/jira/browse/JCR-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

angela updated JCR-996:

    Attachment: JCR_996_spi_3.patch

Included tobis suggestions:

- additional method Path.getString
- additional method Path.Element.getString

and define PathFactory.create(String) to require a String in the format of
Path.getString (thus leaving 'toString' to the implementation)

> 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, JCR_996_spi_2.patch, JCR_996_spi_3.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.

View raw message