Hi, On Wed, Jan 6, 2010 at 9:14 PM, Carsten Ziegeler <[email protected]> wrote: > ...currently our scripting core depends on the jcr api. This is an old > relict to support the optional binding for currentNode. If the current > resource is adaptable to a jcr node, then this binding is set to this node. > This binding is not officially supported :)...
As Google search for "sling currentnode" shows, there are quite a number of examples (in addition to our own docs) which refer to this currentNode binding. So I agree we others that we should keep it, Justin's proposed SlingScriptBindingValuesProvider looks like a good idea. -Bertrand
