Gnome/OpenJDK system-wide proxy definition

[G.M.]

Hi,

An application that I use (to name it: weka [1], written in java) uses the (new?) possibility of java to access the system-wide proxy definition, through the System Property: System.setProperty("java.net.useSystemProxies", "true") [2,3,4].

The sources of the DefaultProxySelector refer to a native method for getting the system-wide proxy definition. I was unable to quickly find the source code of this method, but reading some internet forums, I discovered that the only place they are looking for is the Gnome's definition of the proxy.

Therefore, I googled a little bit on how Gnome defines the proxy, and discovered at least 6 means to do so:
1) gsettings set org.gnome.system.proxy.*
2) dconf write '/system/proxy/http/*'
3) gconftool --set -t string '/system/proxy/*'
4) gconftool-2 --set -t string '/system/proxy/*'
5) gnome-control-panel -> Network -> Proxy
6) gconf-editor GUI: /system/http_proxy/host

Unfortunately, only the last solution finally allowed me to get my grips on the strange value that weka insisted on using for the proxy.

So I'm not sure what I should do with all that information... I'd like to file at least two bugs:

- On OpenJDK. Indeed, I don't understand, since java is mainly commandline, why they insist in not using the environment variables *_proxy that the user or any gnome/kde/etc. tools can easily configure?

- On Gnome. Some day someone will have to explain to me why gnome developers insists in creating multiple complicated ways of doing things that finally do not work, when there exits a simple way that have proved to work perfectly for years...

What do you think?

Cheers

GM
[1] http://www.cs.waikato.ac.nz/ml/weka/
[2] http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html (section 4)
[3] http://www.docjar.com/html/api/java/net/ProxySelector.java.html
[4] http://www.docjar.com/html/api/sun/net/spi/DefaultProxySelector.java.html

[Paul White (paulw2u)]

This issue has sat with without any response for over ten years now so it is being closed as 'Invalid'. I'm not seeing any 'version' information that would point a developer towards the Ubuntu release that needs fixing and of course any such release would now be 'end-of-life' after all this time.

Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu making sure that you tell us in which release(s) you still experience this issue. Any such reinstatement of the bug report should also involve the assigning of a package within the Ubuntu project. https://wiki.ubuntu.com/Bugs/FindRightPackage will help to assign that package.