Unexpected results when using archive_x with cache_archive tags

As per the technotes at http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/applet_caching.html, archive_x tag should be ignored when cache_archive is also present in the html. However, for the following scenarios, this is not working as expected:

1.BothValid1: archive_x has jar files: MainTest.jar with version 1.0.0.0 and Test2.jar with versio 2.0+. cache_archive also has both the jar files.
Jar files at server: MainTest.jar(version.xml), Test2_V2.0.jar, Test2.jar
Expected Result: MainTest.jar and Test2.jar should be cached with no version attached to them.
Actual Result: MainTest.jar and Test2.jar are cached with versions given in archive_x tags, i.e. 1.0.0.0 and 2.0+ respectively.
Test file location: http://129.145.161.175:8080/mytests/Mixed/BothValid1/Test.html

2. BothValid2: archive_x has jar files: MainTest.jar with version 1.0.0.0 and Test2.jar with versio 2.0+. cache_archive also has both the jar files but with versions 2.0.0.0 and 2.1.0.0 defined using cache_version tag.
Jar files at server: MainTest.jar(version.xml), Test2_V2.0.jar, Test2.jar
Expected Result: MainTest.jar and Test2.jar should be cached with versions 2.0.0.0 and 2.1.0.0 attached to them.
Actual Result: MainTest.jar and Test2.jar are cached with versions given in archive_x tags, i.e. 1.0.0.0 and 2.0+ respectively.
Test file location: http://129.145.161.175:8080/mytests/Mixed/BothValid2/Test.html

For both the above cases, cache_archive is getting ignored instead of archive_x tag.

3. BothValid3: archive_x has jar files: MainTest.jar with version 1.0.0.0 and Test2.jar with versio 2.0+. cache_archive also has both the jar files but with versions 2.0.0.0 and 2.1.0.0.
Jar files at server: MainTest.jar, Test2.jar
Expected Result: MainTest.jar and Test2.jar should be cached with versions 2.0.0.0 and 2.1.0.0 attached to them.
Actual Result: MainTest.jar and Test2.jar are cached with versions given in archive_x tags, i.e. 1.0.0.0 and 2.0+ respectively.
Test file location: http://129.145.161.175:8080/mytests/Mixed/BothValid3/Test.html

4. BothValid4: archive_x has jar files: MainTest.jar with version 2.0.0.0 and Test2.jar with version 3.0+. cache_archive also has both the jar files but with versions 2.0.0.0 and 2.1.0.0.
Jar files at server: MainTest.jar, Test2_V2.0.jar, Test2.jar
Expected Result: MainTest.jar and Test2.jar should be cached with versions 2.0.0.0 and 2.1.0.0 attached to them.
Actual Result: MainTest.jar and Test2.jar are cached with versions given in archive_x tags, i.e. 2.0.0.0 and 3.0+ respectively even though the jar files on the server have a lower version attached to them.
Test file location: http://129.145.161.175:8080/mytests/Mixed/BothValid4/Test.html
The versions are being taken from archive_x tags even though the versions specified are invalid.

5. BothValid5: archive_x has jar files: MainTest.jar with version 1.0.0.0 and Test2.jar with version 2.0+. cache_archive also has both the jar files but with versions 2.0.0.0 and 2.1.0.0.
Jar files at server: MainTest_V1.0.jar, Test2_V2.0.jar
Expected Result: Applet should fail to load as cache_archive will not get ant jar files.
Actual Result: Applet fails to load as expected.
Test file location: http://129.145.161.175:8080/mytests/Mixed/BothValid5/Test.html
This is the only case where archive_x was ignored.

Deployment cache was cleared everytime before running the tests. Tests were run on Windows Vista with IE8.