Key objects passed to Rhino context should be Scriptable

Description

Currently, we pass in several objects to the rhino context, such as ScriptUtils (as utils). These are passed in as normal Java classes, which means various extra Java methods are available on them, and they can show up a little oddly in debuggers etc

If we make these objects implement Scriptable from Rhino, then they show up as normal javascript objects, and these issues go away

Environment

None

Testcase ID

None

Activity

Show:
All Replies
October 31, 2020, 1:12 AM

[This issue has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The reporter of this issue was nburch]

All Replies
January 22, 2016, 2:43 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was resplin] This issue was reported against an old version of Alfresco Community Edition.

Alfresco 5.1 is nearing release, and contains many improvements that address old problems. We are closing old issues so that we can better prioritize our efforts.

If you verify that the issue still exists in an Early Access release of Alfresco 5.1, please reopen the issue. If you have any trouble reopening the issue, then leave a comment or email us at community@alfresco.com so that we can assist.

Thank you for collaborating with us on improving Alfresco.

All Replies
March 16, 2015, 10:33 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was resplin] I reopened this issue, and I logged an issue to fix the wolkflow so that external users can reopen issues.

All Replies
March 16, 2015, 8:21 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was nburch] This still applies in Alfresco 5.0. If you fire up Eclipse, and look at the class+interface hierarchy for classes injected into the JS context (eg ScriptUtils), you'll see that they still lack Scriptable, and hence have java methods on them which "enterprising" JS programmers could play with

Also, non-Alfresco users don't seem to have the re-open permissions...

All Replies
March 13, 2015, 6:23 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was resplin] This issue was reported against an old version of Alfresco Community Edition.

Alfresco 5.0 was recently released, and contains many improvements that address old problems. We are closing old issues so that we can better prioritize our efforts.

If you verify that the issue still exists in Alfresco 5.0, please reopen the
issue.

Thank you for collaborating with us on improving Alfresco.

Sincerely,

Richard Esplin
Product Manager, Alfresco Community Edition

Won't Fix

Assignee

All Replies

Reporter

All Replies