-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b54
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082263 | emb-9 | Andy Herrick | P2 | Resolved | Fixed | b54 |
| JDK-8086346 | 8u65 | Andy Herrick | P2 | Resolved | Fixed | b01 |
| JDK-8073766 | 8u60 | Andy Herrick | P2 | Closed | Fixed | |
| JDK-8137412 | emb-8u65 | Unassigned | P2 | Resolved | Fixed | b01 |
| JDK-8076821 | emb-8u60 | Andy Herrick | P2 | Resolved | Fixed | team |
The junit tests SetupHelpers create RuleAction with third arg as an empty string.
This is the <message> arg, so to a run rule - it has created run rule with an empty message.
After 8073589 implementation that will cause an empty message box.
I propose to fix in two places:
1.) pass null, instead of empty string to RuleAction constructor (in SetupHelpers).
2.) only show new dialog in SandboxSecurity.checkRunRuleMessage() if message element is both non-null and non-empty.
This is the <message> arg, so to a run rule - it has created run rule with an empty message.
After 8073589 implementation that will cause an empty message box.
I propose to fix in two places:
1.) pass null, instead of empty string to RuleAction constructor (in SetupHelpers).
2.) only show new dialog in SandboxSecurity.checkRunRuleMessage() if message element is both non-null and non-empty.
- backported by
-
JDK-8076821 junit issue after fix to JDK-8073589
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-
(1 relates to)