[
https://issues.apache.org/jira/browse/SLING-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844845#action_12844845
]
Felix Meschberger commented on SLING-514:
-----------------------------------------
> wish I hadn't called the class CurrentNodeBindingsValuesProvider.
This is absolutely no problem.
Since this is an internal class declared as an OSGi component registering a
service, we can just go an rename that class ...
> Expose current session through currentSession binding
> -----------------------------------------------------
>
> Key: SLING-514
> URL: https://issues.apache.org/jira/browse/SLING-514
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: David Nuescheler
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: JCR Resource 2.0.8
>
>
> i think it would be great to expose a currentSession variable in scripting
> similar to the currentNode.
> in a usecase that i ran to recently i needed access to the session and tried
> to go through currentNode.getSession() which didn't work because my
> currentNode did not really exist since it was a synthetic resource that i
> requested.
> of course one can go through the
> request.getResourceResolver().adaptTo(Packages.javax.jcr.Session) to acquire
> the session but i think a short-hand would be nice since this is a very
> common case
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
