[
https://issues.apache.org/jira/browse/SLING-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108723#comment-13108723
]
Markus Joschko commented on SLING-2227:
---------------------------------------
Not sure about the name. It's not only the save. The patch also prevents the
session.refresh.
So if it should reflect the operation more closely it'll be
isSessionSaveOrRefreshRequired which is a bit long.
I tried to condense that to isSessionUpdateRequired.
But I don't mind the name too much.
> 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
