-
Enhancement
-
Resolution: Fixed
-
P2
-
None
-
b40
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8023459 | 7u60 | Joni Gordon | P2 | Resolved | Fixed | b01 |
| JDK-8023402 | 7u51 | Joni Gordon | P2 | Resolved | Fixed | b01 |
| JDK-8023285 | 7u45 | Joni Gordon | P2 | Resolved | Fixed | b08 |
If an applet is using Live Connect, and does javascript to java calls to the code in the applet, then the mixed code dialog will be avoided if there is a DRS run rule for the applet code being called.
But if the javascript to java code goes directly to the JRE java code, you will need a DRS run rull specifying just the location where the javascript is.
All other location rules apply. for example, the rule:
<rule>
<id location="*.oracle.com"/>
<action permission="run"/>
</rule>
will allow javascript to java calls into the JRE for any html page hosted on any sub-domain of oracle.com.
But if the javascript to java code goes directly to the JRE java code, you will need a DRS run rull specifying just the location where the javascript is.
All other location rules apply. for example, the rule:
<rule>
<id location="*.oracle.com"/>
<action permission="run"/>
</rule>
will allow javascript to java calls into the JRE for any html page hosted on any sub-domain of oracle.com.
- backported by
-
JDK-8023285 Document DSR rule for liveconnect and mixed code in the JRE.
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8021299 DRS: Mixed code dialog for javascript to java call should be suppressed if DRS run rule is in effect for called artifact
-
- Closed
-