PROBLEM:
JNLP file association does not work on cinnabar-linux/GNOME

DESCRIPTION:
The following 4 tests fail on Cinnabar-Linux (x86) with gnome 2.6.1.
suite_javaws_association/check
suite_javaws_association/prompt_user
suite_javaws_association/new_only
suite_javaws_association/replace

They fail with 1.5.0_07-b02 and also with 1.5.0_07-ea-b01 and 1.5.0_06-b05.
They pass on suse10pro (gnome 2.12.0) and on win2000pro with 1.5.0_07-b02.

FAILURE RESULTS AREA:
http://latte.ireland/export/home0/results/1.5.0_07/Build02/deployment/javaws/x86-CinnabarLinux-ff107/4F/

NOTES:
${/USER_HOME/}/.gnome/applications-info/ AND ${/USER_HOME/}/.gnome/mime-info/ were empty. It appeared that no files etc were ever created in these locations during test runs.

The workspace I was using is /net/jqa.ireland/jqa6/dtf/dtf_ws/suites/ssv_tiger_workspace. ssv_tiger_workspace is a child of /net/jsqalab.sfbay/quality1/deployment1/deployment_tiger_UR1_int_ws
I can't find Gnome2.6.1, so I tested 1.5.0_07-b02 on Gnome2.6.0(JDS3) and Gnome2.10(SUSE9.3). Both of them can create the files needed by creating association correctly under ~/.gnome/applications-info/ and ~/.gnome/mime-info/ .
Even these files could be created on SUSE10pro and the testcase passed, the association can't work because the mime system have changed.(see bug's comment in Mustang).
I have fixed this bug in Mustang by that don't support association since Gnome2.8+, and javaws don't create the files needed by creating association any more if Gnome's version is higher than 2.8. The experience of user don't change for this fix, so I don't think it worth to backport in tiger.