From 8e45b5544ad55ff5f6ac6603394be612efe4f322 Mon Sep 17 00:00:00 2001 From: Oliver Gierke Date: Thu, 20 Nov 2008 16:27:35 +0000 Subject: [PATCH] * minor documentation fixes git-svn-id: svn+ssh://svn.synyx.de/var/svn/synyx/opensource/hera/trunk@3474 5a64d73e-33d6-4ccc-9058-23f8668ecac9 --- hera-metadata/src/doc/metadata.xml | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/hera-metadata/src/doc/metadata.xml b/hera-metadata/src/doc/metadata.xml index 2c4fea1..35713d6 100644 --- a/hera-metadata/src/doc/metadata.xml +++ b/hera-metadata/src/doc/metadata.xml @@ -42,13 +42,14 @@ public interface MetadataProvider { linkend="core.plugin-registry" />) without bothering developers with too much information required. - The MetadataProvider interface is to be used in application plugin - interfaces to indicate that they can provide metadata. To ease plugin - implementation we provide AbstractMetadataBasedPlugin that uses the - internal metadata to implement supports(..) method of Plugin. Extending - this base class plugins with metadata as selection criteria can easily be - build. This way you could store the metadata in user specific - configuration files and use this to select a distinct plugin specific to a - given user. + The MetadataProvider interface is to + be used in application plugin interfaces to indicate that they can provide + metadata. To ease plugin implementation we provide + AbstractMetadataBasedPlugin that uses the internal + metadata to implement supports(..) method of + Plugin. Extending this base class plugins + with metadata as selection criteria can easily be build. This way you + could store the metadata in user specific configuration files and use this + to select a distinct plugin specific to a given user. - + \ No newline at end of file