You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/01/21 15:12:34 UTC

[jira] Resolved: (SLING-154) Allow access to Node and Property Methods on ScriptableNode and ScriptableProperty

     [ https://issues.apache.org/jira/browse/SLING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-154.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Felix Meschberger

Implemented in Rev. 613895:

Added more scriptable mappings:
   - Completed getters for ScriptableNode
   - Created ScriptableProperty to map properties
   - Added getters for child nodes (node.children) and
     properties (node.properties) to ScriptableNode

All parameter-less getter methods as well as some "isXXX" methods, such as isNew and isModified are now mapped to ScriptableNode and ScriptableProperty properties.

Please report back if this suites your need or not. Thanks.

> Allow access to Node and Property Methods on ScriptableNode and ScriptableProperty
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-154
>                 URL: https://issues.apache.org/jira/browse/SLING-154
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: David Nuescheler
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> I would like to propose access to all jcr Node methods from ScriptableNode and access to the jcr Property.
> I recently wanted to access the Property.getLength() method from a .esp script and didn't find a good way starting
> out from my very convenient ScriptableNode.
> This discussion already talks about a similar issue:
> http://www.mail-archive.com/sling-dev@incubator.apache.org/msg01481.html
> So ideally somthing like an automatic getter mapping that I know from earlier rhino projects would mean 
> that I could access the same information through for example prop.length or prop.getLength().
> I think it would be great if all jcr Property and Node methods would be exposed, otherwise we are hiding jcr features from
> the script user. I think maybe the solution also requires a ScriptableProperty.
> WDYT?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.