JDK-8140273 : Restore use of CompositeOperation.contains where it is needed
  • Type: Bug
  • Component: core-libs
  • Sub-Component: jdk.nashorn
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2015-10-21
  • Updated: 2015-11-12
  • Resolved: 2015-10-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b89Fixed
Related Reports
Relates :  
JDK-8139931 - Introduce Operation objects in Dynalink instead of string encoding
Description
After JDK-8139931, the test/script/basic/JDK-8023630.js fails.

The reason is a fairly late change to 8139931 where all uses of the (in the end removed) CompositeOperation.contains() method were replaced with NashornCallSiteDescriptor.getFirstStandardOperation(). Unfortunately, uses within JavaSuperAdapterLinker and ReflectionCheckLinker should have been left as-is using CompositeOperation.contains(). 

Solution is to reinstantiate CompositeOperation.contains() and make sure JavaSuperAdapterLinker and ReflectionCheckLinker use them accordingly.