[
https://issues.apache.org/jira/browse/SLING-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-73:
-----------------------------------
Description:
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.
was: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).
Summary: Provided SlingRequestContext to scripts (was: Session is not
saved for POST scripts nor is it made available to the script)
Adapting issue summary to reflect the concrete request (as I understand it)
> 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
> 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.
