Device importer registering

Identifier:

org.eclipse.mtj.core.deviceImporter

Since:

[Enter the first release in which this extension point appears.]

Description:

The device importer extension point provides a means for registering new types of device importers. Devices are fully-formed at import time by the appropriate instance of IDeviceImporter. These device instances are then stored and loaded automatically by the system as necessary. Implementors of this extension point must provide instances of the org.eclipse.mtj.core.importer.IDeviceImporter interface.

Configuration Markup:

<!ELEMENT extension (importer+)>

<!ATTLIST extension

point CDATA #REQUIRED

id CDATA #IMPLIED

name CDATA #IMPLIED>

point - a fully qualified identifier of the target extension point
id - an optional identifier of the extension instance
name - an optional name of the extension instance

<!ELEMENT importer EMPTY>

<!ATTLIST importer

id CDATA #REQUIRED

priority CDATA #REQUIRED

name CDATA #IMPLIED

class CDATA #REQUIRED>

id - a required fully-qualified identifier for this particular device importer extension
priority - the priority order for this importer. The priorty may range from 1 to 99. The importers will be consulted in priority order starting with the lower numbered priority and working toward the highest numbered priority. The first device importer that requires a non-null result for a particular folder will "win" and no further importer instances will be consulted.
name - an optional displayable name for this particular device importer extension
class - the required implementation class for the org.eclipse.mtj.core.importer.IDeviceImporter interface

Examples:

[Enter extension point usage example here.]

Supplied Implementation:

[Enter information about supplied implementation of this extension point.]

Copyright (c) 2003,2008 Craig Setera and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Contributors: Craig Setera (EclipseME) - Initial implementation; Diego Sandin (Motorola) - Refactoring extension name to follow eclipse standards