-
Enhancement
-
Resolution: Won't Fix
-
P3
-
6u17-rev
-
x86
-
windows_2003
Customer is using a large Windows Client network (Terminal Server based) and roll out a network wide customized deployment.properties file.
The customer complain that this deployment.properties file is always overwritten as soon a java application is started, or simply when just open / close the Java control panel.
The order of the customized defined entries seems rewritten, some values are silent gone, some values are silent added.
The bad situation is, that some of these entries, added to deployment.properties file are nowhere documented, or described.
Even the behavior of this itself, why everything will be re-sorted and overwritten is not documented.
This RFE scope is, to request a more complete documentation about all possible deployment.properties file entries.
If a file entry is on status "undocumented" and should be keep "undocumented"
then this documentation should note it, that it will not be documented
due to possible future java architecture changes.
Steps to reproduce:
0) setup a windows system (XP or any other)
1) Install Java for Business or JavaSE 1.5.0_xx and then parallel 1.6.0_xx
2) create a customized "user level" (not system wide) deployment.properties file like this:
#
# my company
# Java Deployment Config file Version 1.009
# date yyyy-mm-dd hh:mm
#
deployment.proxy.type=3
deployment.cache.max.size=20
deployment.cache.jarcompression=9
deployment.console.startup.mode=HIDE
deployment.capture.mime.types=true
deployment.user.cachedir=C:\\Dokumente und Einstellungen\\Administrator\\Sun\\Java\\Deployment\\cache
deployment.user.logdir=C:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\log
deployment.user.tmp=C:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\tmp
deployment.javaws.autodownload=NEVER
deployment.javaws.viewer.bounds=0,0,685,485
deployment.system.tray.icon=true
deployment.browser.vm.iexplorer=true
deployment.browser.vm.mozilla=true
deployment.version=1.6.0
#dedicated for OSPlus class running on 1.5 Log/Trace
deployment.javapi.jre.1.5.0_20.args=-Dcom.rubean.drubeans.app.logging.level\=ALL
deployment.javapi.jre.1.5.0_20.osname=Windows
deployment.javapi.jre.1.5.0_20.osarch=x86
deployment.javapi.jre.1.5.0_20.path=C\:\\PROGRAMME\\Java\\jre1.5.0_20jfb
3) Go in Windows to System Properties -> click to open Java Control Panel
4) close the Java Control panel with click at "OK button"
5) review the deployment.properties and see the modified content like this:
#deployment.properties
#Tue Jul 20 13:58:33 CEST 2010
deployment.user.cachedir=C\:\\Dokumente und Einstellungen\\Administrator\\Sun\\Java\\Deployment\\cache
deployment.user.logdir=C\:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\log
deployment.javaws.autodownload=NEVER
deployment.javaws.viewer.bounds=0,0,685,485
deployment.cache.max.size=20
deployment.javaws.cache.update=true
deployment.version=6.0
deployment.cache.jarcompression=9
deployment.user.tmp=C\:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\tmp
deployment.javapi.cache.update=true
deployment.capture.mime.types=true
#Java Deployment jre's
#Tue Jul 20 13:58:33 CEST 2010
deployment.javaws.jre.1.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.args=
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.1.args=-Dcom.rubean.drubeans.app.logging.level\=ALL
deployment.javaws.jre.1.enabled=true
deployment.javaws.jre.1.registered=true
deployment.javaws.jre.0.osarch=x86
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.1.product=1.5.0_20
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\PROGRAMME\\Java\\jre1.6.0_17jfb\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.1.path=C\:\\PROGRAMME\\Java\\jre1.5.0_20jfb\\bin\\javaw.exe
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.1.osarch=x86
deployment.javaws.jre.1.osname=Windows
deployment.javaws.jre.1.platform=1.5
deployment.javaws.jre.0.product=1.6.0_17-rev
6) be aware of that all administrative comments like company name and revision are silent erased
and there are a lot of entries added with no existing documentation, and there is no reason
why some values are added and some (seems default values) are silent erased.
The customer complain that this deployment.properties file is always overwritten as soon a java application is started, or simply when just open / close the Java control panel.
The order of the customized defined entries seems rewritten, some values are silent gone, some values are silent added.
The bad situation is, that some of these entries, added to deployment.properties file are nowhere documented, or described.
Even the behavior of this itself, why everything will be re-sorted and overwritten is not documented.
This RFE scope is, to request a more complete documentation about all possible deployment.properties file entries.
If a file entry is on status "undocumented" and should be keep "undocumented"
then this documentation should note it, that it will not be documented
due to possible future java architecture changes.
Steps to reproduce:
0) setup a windows system (XP or any other)
1) Install Java for Business or JavaSE 1.5.0_xx and then parallel 1.6.0_xx
2) create a customized "user level" (not system wide) deployment.properties file like this:
#
# my company
# Java Deployment Config file Version 1.009
# date yyyy-mm-dd hh:mm
#
deployment.proxy.type=3
deployment.cache.max.size=20
deployment.cache.jarcompression=9
deployment.console.startup.mode=HIDE
deployment.capture.mime.types=true
deployment.user.cachedir=C:\\Dokumente und Einstellungen\\Administrator\\Sun\\Java\\Deployment\\cache
deployment.user.logdir=C:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\log
deployment.user.tmp=C:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\tmp
deployment.javaws.autodownload=NEVER
deployment.javaws.viewer.bounds=0,0,685,485
deployment.system.tray.icon=true
deployment.browser.vm.iexplorer=true
deployment.browser.vm.mozilla=true
deployment.version=1.6.0
#dedicated for OSPlus class running on 1.5 Log/Trace
deployment.javapi.jre.1.5.0_20.args=-Dcom.rubean.drubeans.app.logging.level\=ALL
deployment.javapi.jre.1.5.0_20.osname=Windows
deployment.javapi.jre.1.5.0_20.osarch=x86
deployment.javapi.jre.1.5.0_20.path=C\:\\PROGRAMME\\Java\\jre1.5.0_20jfb
3) Go in Windows to System Properties -> click to open Java Control Panel
4) close the Java Control panel with click at "OK button"
5) review the deployment.properties and see the modified content like this:
#deployment.properties
#Tue Jul 20 13:58:33 CEST 2010
deployment.user.cachedir=C\:\\Dokumente und Einstellungen\\Administrator\\Sun\\Java\\Deployment\\cache
deployment.user.logdir=C\:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\log
deployment.javaws.autodownload=NEVER
deployment.javaws.viewer.bounds=0,0,685,485
deployment.cache.max.size=20
deployment.javaws.cache.update=true
deployment.version=6.0
deployment.cache.jarcompression=9
deployment.user.tmp=C\:\\DOKUME~1\\ADMINI~1\\LOKALE~1\\Temp\\FI-JRE\\tmp
deployment.javapi.cache.update=true
deployment.capture.mime.types=true
#Java Deployment jre's
#Tue Jul 20 13:58:33 CEST 2010
deployment.javaws.jre.1.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.args=
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.1.args=-Dcom.rubean.drubeans.app.logging.level\=ALL
deployment.javaws.jre.1.enabled=true
deployment.javaws.jre.1.registered=true
deployment.javaws.jre.0.osarch=x86
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.1.product=1.5.0_20
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\PROGRAMME\\Java\\jre1.6.0_17jfb\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.1.path=C\:\\PROGRAMME\\Java\\jre1.5.0_20jfb\\bin\\javaw.exe
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.1.osarch=x86
deployment.javaws.jre.1.osname=Windows
deployment.javaws.jre.1.platform=1.5
deployment.javaws.jre.0.product=1.6.0_17-rev
6) be aware of that all administrative comments like company name and revision are silent erased
and there are a lot of entries added with no existing documentation, and there is no reason
why some values are added and some (seems default values) are silent erased.