From dccc560e9bbbde409fbd9aed70d129078e863fa0 Mon Sep 17 00:00:00 2001 From: Oliver Gierke Date: Tue, 20 Jan 2009 20:38:25 +0000 Subject: [PATCH] Fixed #52. git-svn-id: svn+ssh://svn.synyx.de/var/svn/synyx/opensource/hera/trunk@4078 5a64d73e-33d6-4ccc-9058-23f8668ecac9 --- hera-core/src/doc/core.xml | 33 ++++++++++++++++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/hera-core/src/doc/core.xml b/hera-core/src/doc/core.xml index 025bc7d..9f7ceca 100644 --- a/hera-core/src/doc/core.xml +++ b/hera-core/src/doc/core.xml @@ -154,6 +154,37 @@ public class HostImpl implements Host { installed Spring IDE, you should get code completion on filling the class attribute. + + + Using inner beans + + + This feature is only available for version 0.3 and above! + + + The listing above features an indirection for the + plugin bean definition. Defining the plugin list as top + level bean can have advantages: you easily could place all plugin lists + in a dedicated configuration file, presenting all application extension + points in one single place. Nevertheless you also might choose to define + the list directly in the property declaration: + + + Using internal bean definition + + <import resource="classpath*:com/acme/**/plugins.xml" /> + +<bean id="host" class="com.acme.HostImpl"> + <property name="plugins"> + <plugin:list class="org.acme.MyPluginInterface" /> + </property> +</bean> + + + This way you have a more compact configuration, paying the prica + of tangling all extention points though possibly various config + files. +
@@ -253,4 +284,4 @@ registry.getPluginsFor(ProductType.HARDWARE, new MyException("Damn!");
- + \ No newline at end of file