Hi,

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 :)

We should definitly either remove the dependency to jcr or make it
optional. This allows to use the scripting in a non jcr environment.

I think we should remove this support completly - afaik the only
scripting language that is affected by this change is the javascript
implementation. We could simply add the binding in this scripting
language. JSPs are not affected as we have a taglib there anyway.

So if noone objects, I'll remove the support from the scripting core and
add it to the javascript implementation.

As an alternative we could make the dependency optional and leave this
non official stuff in the core.

WDYT?

Carsten
-- 
Carsten Ziegeler
[email protected]

Reply via email to