JDK-8041123 : DRS: messaging is incorrect when blocking due to DRS version mismatch
  • Type: Bug
  • Component: deploy
  • Affected Version: 7u40,8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-04-18
  • Updated: 2014-07-29
  • Resolved: 2014-05-14
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.
8u20 b15Fixed 9Fixed
When the deployment rule for an application requires a version that is not the latest installed, and does not match the version requested by the app, The application will block as is expected, however the dialog says (for example where application has requested "1.8+" and DRS requires "1.7*):

title: "Application Blocked by Deployment Rule Set"  (correct)
reason: "Deployment Rule Set required version 1.7* not available" (not correct)

The reason the app is blocking is not that 1.7* is not available, but that it doesn't match the version specified by the application.

we need to change the text of the reason to better indicate why we are blocking.

This does not apply to DRS version 1.1 when new force attribute is set to true, but applies to version 1.0 or 1.1 when force attribute is false.

testcase: Install DRS from /java/deployment/www/tests/policy/DeploymentRuleSet.demo.jar (need to import cert from /java/deployment/www/tests/policy/cert.demo.p12 in JCP to user trusted CAcerts) Run applet from demo at: http://oklahoma.us.oracle.com/www/tests/ruleset/version/secure1.7/applet18p.html This should show the dialog . webrev: http://oklahoma.us.oracle.com/www/webrevs/aherrick/1.9.0/8041123/