[ http://issues.apache.org/jira/browse/JCR-416?page=all ]
angela resolved JCR-416.
------------------------
Resolution: Fixed
commited changes with rev. 431546 :
server/io package:
- new interfaces PropertyManager, PropertyHandler, PropertyImportContext,
PropertyExportContext.
- the IOHandler implementations present in the io package now also implement
PropertyHandler.
- DefaultHandler: content nodetype was changed from 'nt:resource' to
'nt:unstructured' . While nt:resource only allows a predefined set of
properties, nt:unstructured contains a residual property definition.
webdav/simple package:
- extend ResourceConfig in order to allow specification of a PropertyManager
and a set of
PropertyHandlers to be used.
- adjust DavResourceImpl: export and import of properties in response to
PROPFIND and
PROPPATCH are delegated to the PropertyManager. This allows to let the
PropertyHandler
decide which properties are exported/imported and how those are stored.
webapp:
- adjust config.xml accordingly
> Webdav Simple: Delegate PROPPATCH to (extended) IOHandlers
> ----------------------------------------------------------
>
> Key: JCR-416
> URL: http://issues.apache.org/jira/browse/JCR-416
> Project: Jackrabbit
> Issue Type: New Feature
> Components: webdav
> Affects Versions: 1.0
> Reporter: angela
> Assigned To: angela
>
> complete description:
> http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/6582
> Proposed solution
> ------------------------------------------------------------------------------------------------------------------------------------
> The situation described before leads me to the following conclusion:
> - IOHandler should not only read/write resource data and properties during
> GET, PUT, PROPFIND but should
> also take care of setting/removing properties upon PROPPATCH.
> - Since the previous suggestion would still limit the properties to
> (jcr:encoding, jcr:mimeType and
> jcr:lastModified), we may think about changing the default nodetype for
> the jcr:content node to
> nt:unstructured.
> I guess this would meet the requirements for those expecting a webDAV server
> that is (as a first step)
> not limited regarding PROPPATCH. Second it would allow to have a handling of
> property modifications
> which is specific for individual resource types instead of trying to set all
> properties to the uppermost node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
