You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Markus Joschko (JIRA)" <ji...@apache.org> on 2011/09/20 14:46:09 UTC
[jira] [Updated] (SLING-2227) Add configuration to skip
session.save in AbstractPostOperation
[ https://issues.apache.org/jira/browse/SLING-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Joschko updated SLING-2227:
----------------------------------
Attachment: session_skip.diff
Patch to skip sessions on request attribute
> Add configuration to skip session.save in AbstractPostOperation
> ---------------------------------------------------------------
>
> Key: SLING-2227
> URL: https://issues.apache.org/jira/browse/SLING-2227
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Markus Joschko
> Attachments: session_skip.diff
>
>
> With SLING-1725 the postservlet operations have been exposed as services to be consumed by other servlets.
> I use that to create two nodes with the ModifyOperation in one request.
> However the second node creation might fail because of the postprocessors.
> In that case I want to return an error to the user and have nothing stored.
> This can't be done at the moment as the AbstractPostOperation always saves independently from its context (so first node gets saved, second node not).
> I think it makes a lot of sense to let the caller of the operation have control over when the session is saved and introduced a flag to skip the save when requested.
> It is modeled after the isSkipCheckin flag.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira