Laboratoire ICAR » Plateforme TXM

Any feedback for this issue ? is the solution 2 has been implemented ?

I propose this fix in org.txm.rcpapplication.Application.activateProxyService():

            // force active provider as "Manual" on Mac OS X
            if (Util.isMac() && System.getProperty("http.proxyHost") != null && ApplicationWorkbenchAdvisor.getWasFirstLaunch()) { 
                System.out.println("System proxy detected. Force network provider as manual.");
                proxyService.setProxiesEnabled(true); 

IMPORTANT NOTE: Log.info() etc. does NOT work at this level of starting. Therefore a lot of log messages may be skipped during start-up.

Matt, could you check that ApplicationWorkbenchAdvisor.getWasFirstLaunch() is well defined/filled at this starting step?

The purpose here is to force manual provider if a proxy system has been detected but only at first run. Then when user quits TXM the preference is saved.

I used the "firstLaunchAfterInstallation" method which check if the TXM_HOME preference is set. Tested on Linux with Eclipse.

System.getProperty("http.proxyHost") returns null on Mac at this step of starting if we haven't call proxyService.setProxiesEnabled(true); before...
Maybe org.eclipse.core.net overrides these settings by loading the org.eclipse.core.net.prefs file.

I think calling the IProxyService activates it leading to a clearing of the Java proxy system properties, here is a test:

// Display the proxy host
System.err.println(System.getProperty("http.proxyHost"));

Bundle bundle = Platform.getBundle("org.eclipse.ui.ide"); //$NON-NLS-1$
IProxyService  proxyService = null;
if (bundle != null) {
    ServiceReference ref = bundle.getBundleContext().getServiceReference(IProxyService.class.getName());
    if (ref != null)
        proxyService = bundle.getBundleContext().getService(ref);
    }
}

// return null
System.err.println(System.getProperty("http.proxyHost"));

Mail FR: Pour info/trace.
proxyService.setProxiesEnabled(true);
passe bien le provider en manual sous Mac mais uniquement si on a déjà fait la manip suivante au moins une fois dans l'interface des prefs.
- passer en manual
- sauver
- passer en direct
- sauver
- redémarrer TXM avec le fix et ça store bien le "Manual"
Je pense que c'est lié à la gestion des prefs dans org.eclipse.core.net