[ https://issues.apache.org/jira/browse/SLING-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536519 ]
Felix Meschberger commented on SLING-73: ---------------------------------------- I agree, that this needs to be discussed. I therefore started a thread on the list [1] [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg00562.html > Provided SlingRequestContext to scripts > --------------------------------------- > > Key: SLING-73 > URL: https://issues.apache.org/jira/browse/SLING-73 > Project: Sling > Issue Type: Bug > Components: microsling > Reporter: Lars Trieloff > Assignee: Felix Meschberger > Attachments: microsling-save-session-on-post.patch, POST.esp > > > POST scripts (e.g. attached POST.js) cannot have side-effects because the > session is not saved after processing the script. Unfortunately the session > is not made available to the script so the script cannot save the session > itself (which I would consider an ugly workaround). > If the SlingRequestContext would be provided as a scripting variable, the > session would be available and could be saved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.