Fixed #52.
git-svn-id: svn+ssh://svn.synyx.de/var/svn/synyx/opensource/hera/trunk@4078 5a64d73e-33d6-4ccc-9058-23f8668ecac9
This commit is contained in:
@@ -154,6 +154,37 @@ public class HostImpl implements Host {
|
|||||||
installed Spring IDE, you should get code completion on filling the
|
installed Spring IDE, you should get code completion on filling the
|
||||||
class attribute.</para>
|
class attribute.</para>
|
||||||
</simplesect>
|
</simplesect>
|
||||||
|
|
||||||
|
<simplesect>
|
||||||
|
<title>Using inner beans</title>
|
||||||
|
|
||||||
|
<note>
|
||||||
|
<para>This feature is only available for version 0.3 and above!</para>
|
||||||
|
</note>
|
||||||
|
|
||||||
|
<para>The listing above features an indirection for the
|
||||||
|
<code>plugin</code> 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:</para>
|
||||||
|
|
||||||
|
<example>
|
||||||
|
<title>Using internal bean definition</title>
|
||||||
|
|
||||||
|
<programlisting language="xml"><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></programlisting>
|
||||||
|
</example>
|
||||||
|
|
||||||
|
<para>This way you have a more compact configuration, paying the prica
|
||||||
|
of tangling all extention points though possibly various config
|
||||||
|
files.</para>
|
||||||
|
</simplesect>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section>
|
<section>
|
||||||
|
|||||||
Reference in New Issue
Block a user