The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

  PXP::Plugin - Plugin class definition (used only in the
  internal registry)

SYNOPSIS

<?xml version="1.0"?>

<plugin id="IMC::WebApp::TestPlugin" name="Test plugin" version="0.1" provider-name='IDEALX'>

</plugin>

DESCRIPTION

A plugin groups together a set of extensions and/or extension-points.

A PXP::Plugin represents such a container as it is read and its content loaded into the system. A common interface is provided to access the configuration descriptors and the actual implementation that has been loaded into the system.

NOTE: a PXP::Plugin object is NOT a plugin.

A real plugin, is just a set of Perl modules loaded according to the 'plugin.xml' descriptor file.

Plugin dependencies are supported with the <require> tag.

Limitations

We support only a subset of the Eclipse plugin model.

instantiateExtension($class, @args)

Load a perl class ($class) and instantiate a new object of this class, with optional arguments for the object initializer (@args)

Return the new instance or undef if the class could not be loaded

name, id, version, providerName

Basic accessors for plugin properties.

resourceDir

Accessor for the 'resourceDir' attribute. 'resourceDir' points to the directory containing the resources bundled with the plugin, such as config files, templates, etc.

This method is called by the PluginRegistry as it loads the plugin.

SEE ALSO

PXP::PluginRegistry, PXP::ExtensionPoint, PXP::Extension

See the article on eclipse.org describing the plugin architecture : http://www.eclipse.org/articles/Article-Plug-in-architecture/plugin_architecture.html

1 POD Error

The following errors were encountered while parsing the POD:

Around line 476:

You forgot a '=back' before '=head1'