P3
Build Info: Nightly Build from this location
/net/dig-dug.east/bigtmp/deployment/1.6.0/nightly/
The application, which is already exists in the "user" cache, is not getting imported into "system" cache.
Follow these steps to reproduce this bug:
1. Install any PIT or Nightly build
2. Configure the "system" cache by setting up the property "deployment.system.cachedir"
3. Import any application into the "user" cache using the command "javaws -import ${URL}"
4. Now import the same application into the "system" cache by "javaws -system -import ${URL}"
5. Now uninstall the "user" cache, using "javaws -uninstall"
6. Now try to launch the same application using "javaws ${URL}", now javaws starts downloading the application.
The above behaviour is a regression in caching. Ideally javaws should launch the application from the "system" cache, since the same application got imported into "system" cache too.
After uninstalling the "user" cache, you can't view the "system" imported application in the Cache Viewer by selecting the "System Applications". Even if you goto the directory configured for the "deployment.system.cachedir", the ".idx" or "data" files won't be there, only the ".lap" file got created.
The same behaviour can be observed for the applications which got imported into the "system" cache and then into the "user" cache.
This is a regression in the caching mechanism from Tiger, when a same application get imported into "user" and "system", javaws does maintain a copy in both the cache, even if you uninstall any of the cache(user/system), still javaws will launch the application from the uninstalled cache(user/system). But in mustang, this is not happening, since it has only one copy of the application. If any of the cache(user/system) get uninstalled, then javaws will download the application.
###@###.### 2005-04-11 13:51:00 GMT
/net/dig-dug.east/bigtmp/deployment/1.6.0/nightly/
The application, which is already exists in the "user" cache, is not getting imported into "system" cache.
Follow these steps to reproduce this bug:
1. Install any PIT or Nightly build
2. Configure the "system" cache by setting up the property "deployment.system.cachedir"
3. Import any application into the "user" cache using the command "javaws -import ${URL}"
4. Now import the same application into the "system" cache by "javaws -system -import ${URL}"
5. Now uninstall the "user" cache, using "javaws -uninstall"
6. Now try to launch the same application using "javaws ${URL}", now javaws starts downloading the application.
The above behaviour is a regression in caching. Ideally javaws should launch the application from the "system" cache, since the same application got imported into "system" cache too.
After uninstalling the "user" cache, you can't view the "system" imported application in the Cache Viewer by selecting the "System Applications". Even if you goto the directory configured for the "deployment.system.cachedir", the ".idx" or "data" files won't be there, only the ".lap" file got created.
The same behaviour can be observed for the applications which got imported into the "system" cache and then into the "user" cache.
This is a regression in the caching mechanism from Tiger, when a same application get imported into "user" and "system", javaws does maintain a copy in both the cache, even if you uninstall any of the cache(user/system), still javaws will launch the application from the uninstalled cache(user/system). But in mustang, this is not happening, since it has only one copy of the application. If any of the cache(user/system) get uninstalled, then javaws will download the application.
###@###.### 2005-04-11 13:51:00 GMT