JDK-Info:
---------
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b13)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b13, mixed mode, sharing)


System-Info:
------------
Generic


Steps to Reproduce:
-------------------
1) Change the user cache directory location using Java Control Panel ("Settings..." --> "Location:") to an invalid path and Apply Changes

2) Launch javaws:
Fails with reason "The User cache does not exist and cannot be created. Check that the configuration is valid, and that you have permission to write to the configured cache location."

3) Now, change the user cache directory location to NULL (no path specified)

4) Click on settings again
Location displays: /home/rk145013/.java/deployment/cache (default location)

5) But ~/.java/deployment/deployment.properties file still has the entry for the previous invalid path entry

6) Launch javaws:
Fails again with the same reason:
"The User cache does not exist and cannot be created. Check that the configuration is valid, and that you have permission to write to the configured cache location."


Expected Behavior:
------------------
When NULL value is entered for cache location and OK button clicked, User cache Location field on Java Control Panel displays the default value. Hence, either the default location has to be used while launching javaws (or) Apply button has to be enabled to facilitate the changes to be saved even when the user cache location entered is NULL/empty.

Actual Behavior:
----------------
When NULL/empty value is assigned for user cache location, "Location" field displays the default location; but still launches javaws using the last entered location (saved in the properties file)