Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Spaces/Spi/ProviderSpi"
(New page: =How can Eclipse Spaces be extended?= It is possible to extend Eclipse Spaces in the following ways: * Adding a Space Provider - this is done when there is a need to add a new way of acces...) |
(→Space Provider) |
||
| Line 13: | Line 13: | ||
* ISpace | * ISpace | ||
| − | The ISpaceProvider's main responsibility is to create an instance of an ISpace given | + | The ISpaceProvider's main responsibility is to create an instance of an ISpace given an URI that addresses a space. In order to do this, the implementor of ISpaceProvider must specify a name for the <i>providerScheme</i> to use. The <i>providerScheme</i> is part of the URI, and is used as a key by the core spaces implementation to match a URI with an implementation of ISpaceProvider. |
Revision as of 19:56, 18 January 2008
How can Eclipse Spaces be extended?
It is possible to extend Eclipse Spaces in the following ways:
- Adding a Space Provider - this is done when there is a need to add a new way of accessing a space
- Adding UI specific for a Space Provider implementation
- Adding a Publishing Operation - this is done when a new way of writing artifacts into a space is needed
- Adding UI specific for a Publishing Operation
These are described in more detail below
Space Provider
A Space Provider's main responsibility is to implement the following two interaces in the org.eclipse.spaces.core.provider.spi package:
- ISpaceProvider
- ISpace
The ISpaceProvider's main responsibility is to create an instance of an ISpace given an URI that addresses a space. In order to do this, the implementor of ISpaceProvider must specify a name for the providerScheme to use. The providerScheme is part of the URI, and is used as a key by the core spaces implementation to match a URI with an implementation of ISpaceProvider.