[
https://issues.apache.org/jira/browse/JCR-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086950#comment-13086950
]
angela commented on JCR-3054:
-----------------------------
i am fine with deprecating the method.
the only thing that i was thinking of was the question of the same-name node +
property
feature which is allowed since jcr 283. this used to be a problem in the
jcr-remoting
since on the server-side there - up to now - no possibility to distinguish them
path-wise.
(see JCR-1616)... but since the spi-ItemID itself is sufficient to avoid any
ambiguity,
the proposed solution should not do any harm (au contraire).
> Deprecate RepositoryService.getPropertyInfo method
> --------------------------------------------------
>
> Key: JCR-3054
> URL: https://issues.apache.org/jira/browse/JCR-3054
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr2spi, jackrabbit-spi, jackrabbit-spi2dav,
> jackrabbit-spi2jcr
> Affects Versions: 2.3.0
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 2.3.0
>
> Attachments: JCR-3054.patch
>
>
> I would like to deprecate and ultimately remove the
> RepositoryService.getPropertyInfo method and extend
> RepositoryService.getItemInfos to take over that functionality. getItemInfos
> would thus change to
> /**
> * Method used to 'batch-read' from the persistent storage. It returns the
> * <code>ItemInfo</code> for the given <code>ItemId</code> as the first
> * element in the <code>Iterator</code>. In addition the iterator may
> contain
> * arbitrary <code>ItemInfo</code>s.
> */
> public Iterator<? extends ItemInfo> getItemInfos(SessionInfo sessionInfo,
> ItemId itemId) throws ItemNotFoundException, RepositoryException;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
