[ https://issues.apache.org/jira/browse/SLING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reopened SLING-154: ------------------------------------- Reopen because my fix was completely broken. Thanks Bertrand for providing the patch. > 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 > > Attachments: SLING-154.partial.patch > > > 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.