From 04a9aa4287c9845599174e992babd8845d23e549 Mon Sep 17 00:00:00 2001 From: Oliver Gierke Date: Fri, 27 Nov 2009 14:54:32 +0000 Subject: [PATCH] * fixed use of @Factory@ instead of @FactoryPostProcessor@ git-svn-id: svn+ssh://svn.synyx.de/var/svn/synyx/opensource/hera/trunk@8085 5a64d73e-33d6-4ccc-9058-23f8668ecac9 --- core/src/doc/core.xml | 44 +++++++++++++++++++++---------------------- 1 file changed, 21 insertions(+), 23 deletions(-) diff --git a/core/src/doc/core.xml b/core/src/doc/core.xml index 93841a6..646fa74 100644 --- a/core/src/doc/core.xml +++ b/core/src/doc/core.xml @@ -79,7 +79,7 @@ public class HostImpl implements Host {
Collecting Spring beans dynamically - With the BeanListBeanFactoryPostProcessor + With the BeanListBeanFactory Hera provides a Spring container extension, that allows to lookup beans of a given type in the current ApplicationContext and register them as @@ -94,7 +94,7 @@ public class HostImpl implements Host { <property name="plugins" ref="plugins" /> </bean> -<bean class="org.synyx.hera.plugin.support.BeanListBeanFactoryPostProcessor"> +<bean class="org.synyx.hera.plugin.support.BeanListBeanFactory"> <property name="lists"> <map> <entry key="plugins" value="org.acme.MyPluginInterface" /> @@ -114,18 +114,17 @@ public class HostImpl implements Host { automatically as long as it is annotated with @Component, @Service a.s.o. - The BeanListBeanFactoryPostProcessor in turn - allows registering a map of lists to be created, where the maps entry key - is the id under which the list will be registered and the entry's value is - the type to be looked up. + The BeanListBeanFactory in turn allows + registering a map of lists to be created, where the maps entry key is the + id under which the list will be registered and the entry's value is the + type to be looked up. - The design of the - BeanListBeanFactoryPostProcessor might seem a - little confusing at first (especially to set a map on a property named - lists). This is due to the posibility to register more than one list to - be looked up. We think about dropping this functionality for the sake of - simplicity in future versions. + The design of the BeanListBeanFactory might + seem a little confusing at first (especially to set a map on a property + named lists). This is due to the posibility to register more than one + list to be looked up. We think about dropping this functionality for the + sake of simplicity in future versions. @@ -194,12 +193,12 @@ public class HostImpl implements Host { Plugin beans Using plain interfaces and - BeanListBeanFactoryPostProcessor offers an easy way - to dynamically lookup beans in Spring environments. Nevertheless, very - often you face the situation that you want to have dedicated access to a - subset of all plugins, choose plugins by a given criteria or use a decent - default plugin or the like. Thus we need a basic infrastructure interface - for plugin interfaces to extend and a more sophisticated plugin + BeanListBeanFactory offers an easy way to + dynamically lookup beans in Spring environments. Nevertheless, very often + you face the situation that you want to have dedicated access to a subset + of all plugins, choose plugins by a given criteria or use a decent default + plugin or the like. Thus we need a basic infrastructure interface for + plugin interfaces to extend and a more sophisticated plugin container. @@ -268,11 +267,10 @@ registry.getPluginsFor(ProductType.HARDWARE, new MyException("Damn!"); Configuration and namespace - Similar to the - BeanListBeanFactoryPostProcessor described in - Hera provides a - PluginRegistryBeanFactoryPostProcessor to - automatically lookup beans of a dedicated type to be aggregated in a + Similar to the BeanListBeanFactory + described in Hera provides a + PluginRegistryBeanFactory to automatically lookup + beans of a dedicated type to be aggregated in a PluginRegistry. Note that the type has to be assignable to Plugin to let the registry work as expected.