JDK-7083825 : revise the fix for 7074440
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 7-client
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: windows_xp
- CPU: x86
- Submitted: 2011-08-26
- Updated: 2013-09-12
- Resolved: 2011-09-06
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.
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 7 | JDK 8 |
|---|---|
7u2 b04Fixed  |
8Fixed |
Description
Current fix for 7074440 involves caching the dispid when CJavaDispatch::InvokeEx is called and then use the cached dispid later to setup the java name spaces.
Implementation is fragile because:
a) There is no guarantee IE will always perform any calls back to CJavaDispatch after registration
(and then we may do something wrong on first real PROPERTYPUT)
b) There is no guarantee there will be just one call from IE after we register object
c) First real use of CJavaObject may also be PROPERTYPUT and then we may mistakenly ignore it.