466509 - Provide a way to prevent access to individual methods in NativeJavaObject

Status: RESOLVED INACTIVE

(Rhino Graveyard :: Core, enhancement)

Description

[Kevin Ruland]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: 1_7R1

The Rhino NativeJavaObject wraps Java Objects and exposes all public methods to JavaScript.  In some scenarios, certain methods should not be exposed.  The Object.wait and Object.notify are particularly trouble some because they are public, final and can cause threading problems.  In order to hide these methods from JavaScript, the developer of the embedding needs to write ScriptableObject wrappers for all Java objects.

Reproducible: Always

Comment 1

[Kevin Ruland]

Attachment: Patch for JavaMembers, ClassShutter and test case

This patch contains changes to the ClassShutter interface providing an entry developers can use to prevent individual member function from being exposed to JavaScript through the NativeJavaObject.  JavaMembers was changed to call this method during the iteration over Member objects.

It could be possible for this mechanism to be extended/enhanced to cover the Context.FEATURE_ENHANCED_JAVA_ACCESS functionality as well.

Comment 2

[Sylvestre Ledru [:Sylvestre]]

Closing. Bug management is now done here:
https://github.com/mozilla/rhino