Hi, Before SLING-154, the javascript expression "node.text" (in ESP scripts for example) would return the JCR "text" property of the node.
I assume this is the most frequent use case for scripted Nodes: work with their content, so we should make this as natural as possible, for example: node.text -> value of the "text" property of the node node.children.foo -> the "foo" child node Now, we'd like to call JCR methods on the Node object as well - but if we represent JCR getters as javascript properties, like node.path -> call JCR Node.getPath() We get a name collision with a Property that would be called "path". Any ideas on how to best solve this? The simplest way might be to require the use of node.getPath() instead of node.path, and use javascript property names for content access only, not for JCR getters. -Bertrand
