One use case for modifying the default set of protocols would be to set a custom SSL socket factory. This would look something like the following:
Scheme myHTTPS = new Scheme( "https", new MySSLSocketFactory(), 443 ); Scheme.registerScheme( "https", myHTTPS );@author Michael Becke @author Jeff Dever @author Mike Bowler @since 2.0
Scheme https = new Scheme("https", new MySecureSocketFactory(), 443); SchemeRegistry.DEFAULT.register(https);@author Roland Weber @author Michael Becke @author Jeff Dever @author Mike Bowler
Scheme https = new Scheme("https", new MySecureSocketFactory(), 443); SchemeRegistry.DEFAULT.register(https);@author Roland Weber @author Michael Becke @author Jeff Dever @author Mike Bowler
An instance of IScheme
is a handle representing a binding scheme as defined by the extension point org.eclipse.ui.bindings
. The identifier of the handle is the identifier of the scheme being represented.
An instance of IScheme
can be obtained from an instance of ICommandManager
for any identifier, whether or not a scheme with that identifier is defined in the plugin registry.
The handle-based nature of this API allows it to work well with runtime plugin activation and deactivation. If a scheme is defined, that means that its corresponding plug-in is active. If the plug-in is then deactivated, the scheme will still exist but it will be undefined. An attempt to use an undefined scheme will result in a NotDefinedException
being thrown.
This class is not intended to be extended by clients.
@since 3.1 @see ISchemeListener @see org.eclipse.core.commands.CommandManager
|
|
|
|
|
|
|
|
|
|