-
Bug
-
Resolution: Won't Fix
-
P3
-
None
-
6u10
-
x86
-
windows_xp
Java Update is not using modified mapping XML file while showing the update dialog.
How to reproduce
1.) Install 6u10 b26 pit
2.) Set the UpdateServletURL to valid XML file. My XML file
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<java-update-map version="1.0">
<mapping>
<version>1.6.0_10</version>
<url>http://j2se.east.sun.com/deployment/jdp-scratch/deployment/1.6.0_10/pit/2008-06-04.21_16/windows-i586/iftw/1.6.0_11-b326.xml</url>
</mapping>
</java-update-map>
3.) Launch JCP and perform Manual Update via clicking "Update Now" button in update tab. Update dialog is displayed
(Atached screen shot - 6u11Update.JPG)
4.) Click on cancel and modified the map .xml file
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<java-update-map version="1.0">
<mapping>
<version>1.6.0_10</version>
<url>http://j2se.east.sun.com/deployment/jdp-scratch/deployment/1.6.0_10/pit/2008-06-05/windows-i586/iftw/1.6.0_12-b326.xml</url>
</mapping>
</java-update-map>
5.) Repeat step 3 and dialog is still the same. It should have displayed the 6u12 update info
6.) Log off, Wait for 30 minutes and relogin. Repeat step 3 and dialog is still the same. It should have displayed the 6u12 update info
7.) Reboot the machine and Repeat step 3 and update dialog is still the same. It should have displayed the 6u12 update info
8.) Now try on some other machine. Install 6u10 and keep the mapped XML file as mentioned in step 4. Set the UpdateServletURL
9.) Repeat step 3 and it shows the correct update dialog ( See the attached screen shot- 6u12Update.JPG)
10.) Now open the Default browser or IE on same old machine and load the mapping XML file.
11.) Repeat step 3 and it shows the correct update dialog.
This could be the issue with auto update as well. I guess Update is realying on broswer cache and doesn't read/download the modifed XML file.
Please let me know, if you want the machines to reproduce this issue.
How to reproduce
1.) Install 6u10 b26 pit
2.) Set the UpdateServletURL to valid XML file. My XML file
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<java-update-map version="1.0">
<mapping>
<version>1.6.0_10</version>
<url>http://j2se.east.sun.com/deployment/jdp-scratch/deployment/1.6.0_10/pit/2008-06-04.21_16/windows-i586/iftw/1.6.0_11-b326.xml</url>
</mapping>
</java-update-map>
3.) Launch JCP and perform Manual Update via clicking "Update Now" button in update tab. Update dialog is displayed
(Atached screen shot - 6u11Update.JPG)
4.) Click on cancel and modified the map .xml file
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<java-update-map version="1.0">
<mapping>
<version>1.6.0_10</version>
<url>http://j2se.east.sun.com/deployment/jdp-scratch/deployment/1.6.0_10/pit/2008-06-05/windows-i586/iftw/1.6.0_12-b326.xml</url>
</mapping>
</java-update-map>
5.) Repeat step 3 and dialog is still the same. It should have displayed the 6u12 update info
6.) Log off, Wait for 30 minutes and relogin. Repeat step 3 and dialog is still the same. It should have displayed the 6u12 update info
7.) Reboot the machine and Repeat step 3 and update dialog is still the same. It should have displayed the 6u12 update info
8.) Now try on some other machine. Install 6u10 and keep the mapped XML file as mentioned in step 4. Set the UpdateServletURL
9.) Repeat step 3 and it shows the correct update dialog ( See the attached screen shot- 6u12Update.JPG)
10.) Now open the Default browser or IE on same old machine and load the mapping XML file.
11.) Repeat step 3 and it shows the correct update dialog.
This could be the issue with auto update as well. I guess Update is realying on broswer cache and doesn't read/download the modifed XML file.
Please let me know, if you want the machines to reproduce this issue.