[
https://issues.apache.org/jira/browse/SLING-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657545#action_12657545
]
Felix Meschberger commented on SLING-784:
-----------------------------------------
I agree with Toby that mixins should be handled like any other MV properties
protocol-wise.
Internally, the have to be handled differently of course: Instead of just
adding the properties from the request we would have to do:
* Remove mixins not listed in the request
* Add mixins listed in the request, but not set yet
I think this handling should take place in the processCreate method: If the
item exists, just the jcr:mixinTypes parameters are processed if existing.
As for @Delete: I agree, that this should just remove all mixins. This should
be handled in the "processDeletes" method.
> SlingPostServlet does not allow setting mixin types on existing nodes
> ---------------------------------------------------------------------
>
> Key: SLING-784
> URL: https://issues.apache.org/jira/browse/SLING-784
> Project: Sling
> Issue Type: Improvement
> Components: Servlets Post
> Reporter: Alexander Saar
> Attachments: post-servlet-change-mixins.diff
>
>
> the current implementation of the sling POST servlet allows to specify mixin
> node types when a new node is created, but it is not possible to add/change
> mixin node types of existing nodes. I suggest to add this funtionality
> because it is a common use case that you want to set properties which are
> defined in mixin node types (eg adding some meta data to a file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
