Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2206122 | 7 | Sharon Zakhour | P2 | Closed | Fixed | b110 |
J2SE Version (please include all output from java -version flag):
JDK 6u19 build01(SSR 10_01)
Does this problem occur on J2SE 1.4.x or 5.0.x or 6.0? Yes / No (pick one)
No
Operating System Configuration Information (be specific):
Window vista
Hardware Configuration Information (be specific):
x86
Bug Description:
Got the screen display(image01) after finished installing JDK 6u19 build01.
Did have Firefox open during the install.don't know if that is relevant
Vista business 32-bit
<image001.png>
<image002.png>
CAP member just had the need to be able to "brand" their product so it looks
a bit different for a particular client. This really worked well until JDK 6 update 19.
Now there is an extra security dialog that always comes up when the application starts.
<image003.png>
The is probably because the jar file with the branding information is not signed.
They followed the rules and put it in its own JNLP file and everything.
He was very pleased when he got it all to work so well.
This new dialog invalidates the solution they just created. If came up only the
first time it *may* (but probably not) have been acceptable, but every time certainly
will not be. There already is a security dialog and one is enough.
JDK 6u19 build01(SSR 10_01)
Does this problem occur on J2SE 1.4.x or 5.0.x or 6.0? Yes / No (pick one)
No
Operating System Configuration Information (be specific):
Window vista
Hardware Configuration Information (be specific):
x86
Bug Description:
Got the screen display(image01) after finished installing JDK 6u19 build01.
Did have Firefox open during the install.don't know if that is relevant
Vista business 32-bit
<image001.png>
<image002.png>
CAP member just had the need to be able to "brand" their product so it looks
a bit different for a particular client. This really worked well until JDK 6 update 19.
Now there is an extra security dialog that always comes up when the application starts.
<image003.png>
The is probably because the jar file with the branding information is not signed.
They followed the rules and put it in its own JNLP file and everything.
He was very pleased when he got it all to work so well.
This new dialog invalidates the solution they just created. If came up only the
first time it *may* (but probably not) have been acceptable, but every time certainly
will not be. There already is a security dialog and one is enough.
- backported by
-
JDK-2206122 Extra security dialog that always comes up when the application starts
- Closed
- relates to
-
JDK-6911088 VC++ error during JRE installation and uninstalltion with 6u18b07 PIT build on windows
- Closed