|
New Extension Point: URL Stream Handler Service
|
Normally, when creating an instance of java.net.URL, it's necessary to use one of the 'built-in' protocols...e.g. http, ftp, file, etc. Any other protocols
will not have an URLStreamHandler associated with them, and the java.net.URL constructor will throw a MalformedURLException. For example:
// throws MalformedURLException
URL anURL = new URL("foobar://whateverIwanttohave/here/and/there/and/everywhere");
The new ECF filetransfer extension point org.eclipse.ecf.filetransfer.urlStreamHandlerService allows plugins to add new URL protocols
to the Platform, and register a class for handling the parsing of the URL and/or the creation of URLConnection instances (via the URL.openConnection()
method). So, for example the following extension will setup a 'foobar' protocol handler service:
<extension
point="org.eclipse.ecf.filetransfer.urlStreamHandlerService">
<urlStreamHandlerService
protocol="foobar"
serviceClass="org.eclipse.ecf.tests.filetransfer.TestURLStreamHandlerService">
</urlStreamHandlerService>
</extension>
With such an extension defined, and the ECF filetransfer API plugin started, the following code will no longer throw an exception:
// does not throw MalformedURLException
URL anURL = new URL("foobar://whateverIwanttohave/here/and/there/and/everywhere");
URLConnection connection = anURL.openConnection();
Note that the 'serviceClass' must be a valid subclass of org.osgi.service.url.AbstractURLStreamHandlerService.
Here is a trivial example implementation class:
public class TestURLStreamHandlerService extends
AbstractURLStreamHandlerService {
}
/* (non-Javadoc)
* @see org.osgi.service.url.AbstractURLStreamHandlerService#openConnection(java.net.URL)
*/
public URLConnection openConnection(URL u) throws IOException {
return new TestHttpURLConnection(u);
}
}
See also the extension point documentation for the org.eclipse.ecf.filetransfer.urlStreamHandlerService extension point.
|
