This page (revision-6) was last changed on 19-Dec-2012 06:12 by Volker Belli

This page was created on 17-Dec-2012 09:45 by LukasBrehl

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
6 19-Dec-2012 06:12 2 KB Volker Belli to previous
5 19-Dec-2012 06:11 2 KB Volker Belli to previous | to last
4 19-Dec-2012 06:08 2 KB Volker Belli to previous | to last
3 17-Dec-2012 16:38 2 KB constin to previous | to last
2 17-Dec-2012 16:13 2 KB Jochen Reutelshöfer to previous | to last
1 17-Dec-2012 09:45 2 KB LukasBrehl to last

Page References

Incoming links Outgoing links
Meaning of plugin.xml
Meaning of plugin.xml

Version management

Difference between version and

At line 1 changed 2 lines
!!! The plugin.xml
The d3web software makes heavy use of plugins to extend its functionalities, using the JPF plugin-framework ([JPF|http://jpf.sourceforge.net/]). The plugins need to be configured using plugin.xml files in each binary project (jar-archive).
!!!plugin.xml
At line 3 added 3 lines
The general structure of the XML file is described in the [JPF tutorial|http://jpf.sourceforge.net/de/tutorial.html].
Therefore, we focus on the parts, that are specific for the d3web development.
A minimalistic example defining only one {{ExtensionPoint}} is given as follows:
At line 6 changed one line
!! Add extensions using an existing extension-point
%%prettify
{{{
<?xml version="1.0" ?>
<!DOCTYPE plugin PUBLIC "-//JPF//Java Plug-in Manifest 1.0" "http://jpf.sourceforge.net/plugin_1_0.dtd">
<!-- This plugin only defines extension points for CasePersistenceHandler and CaseConversionHandler. -->
<plugin id="de.d3web.casepersistence" version="0.0.1">
<extension-point id="CasePersistenceHandler">
<parameter-def id="class" />
<parameter-def id="name" />
<parameter-def id="description" />
<parameter-def id="version" />
<parameter-def id="priority" type="number" />
</extension-point>
</plugin>
}}}
/%
At line 8 removed 4 lines
A plugin can define new extension points, but can also extend existing extension points of other plugins.
The defined extension point specifies that each extension has to give values for class, name, description, version, and priority.
This has to be defined by each extension point; an extension point further can require additional value, for example the specification of a file name.
At line 63 added 3 lines
A plugin can define new extension points, but can also extend existing extension points of other plugins.
The defined extension point specifies that each extension has to give values for class, name, description, version, and priority.
This has to be defined by each extension point; an extension point further can require additional value, for example the specification of a file name.
At line 49 removed 25 lines
!! Define new extension-points
A minimalistic example defining only one {{ExtensionPoint}} is given as follows. See also [How-To Extension Points] for more details on writing your own extensions:
%%prettify
{{{
<?xml version="1.0" ?>
<!DOCTYPE plugin PUBLIC "-//JPF//Java Plug-in Manifest 1.0" "http://jpf.sourceforge.net/plugin_1_0.dtd">
<!-- This plugin only defines extension points for CasePersistenceHandler and CaseConversionHandler. -->
<plugin id="de.d3web.casepersistence" version="0.0.1">
<extension-point id="CasePersistenceHandler">
<parameter-def id="class" />
<parameter-def id="name" />
<parameter-def id="description" />
<parameter-def id="version" />
<parameter-def id="priority" type="number" />
</extension-point>
</plugin>
}}}
/%
%%tags
plugin.xml
%
This page (revision-6) was last changed on 19-Dec-2012 06:12 by Volker Belli Top