[
https://issues.apache.org/jira/browse/SLING-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435165#comment-17435165
]
Konrad Windszus commented on SLING-10888:
-----------------------------------------
The question is which input parameters should be considered for such an API?
Only path or in general all parameters which would be passed to the according
CRUD operation. Checking certain conditions upfront for the JCR provider is
sometimes complex (like mandatory properties missing in create) and also may be
changed by subsequent CRUD operations (like adding additional properties) so I
wonder how far we should go with the capabilities check.
> Add CRUD operation capability API
> ---------------------------------
>
> Key: SLING-10888
> URL: https://issues.apache.org/jira/browse/SLING-10888
> Project: Sling
> Issue Type: New Feature
> Components: API
> Reporter: Konrad Windszus
> Priority: Major
>
> As not all resource providers necessarily support all CRUD operations it
> would be beneficial to have some API to check in advance if certain CRUD
> operations are supported at a certain path.
> Currently the only way is to try it out and afterwards deal with the
> exceptions.
> There are potentially different support levels for each operation:
> # Supported with these parameters (might not only depend on the path, but
> also on other parametrisation like properties for creating resources. This is
> the case for mandatory properties in certain node types in the JCR provider)
> # Not supported in general by the underlying resource provider
> # Not supported with these parameters
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
