[
https://issues.apache.org/jira/browse/HIVEMIND-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Hügen resolved HIVEMIND-84.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha-1
hivemind 2 configuration types are not restricted to lists
> BuilderFactory support for typed configurations instead of lists
> ----------------------------------------------------------------
>
> Key: HIVEMIND-84
> URL: https://issues.apache.org/jira/browse/HIVEMIND-84
> Project: HiveMind
> Issue Type: Improvement
> Components: framework
> Affects Versions: 1.1
> Reporter: Achim Hügen
> Priority: Minor
> Fix For: 2.0-alpha-1
>
> Attachments: typed-configuration-patch.zip
>
>
> What always bothered me is the need to define configuration properties or
> parameters as java.util.List
> even if the configuration has a single contribution only (defined with
> occurs="1" or occurs="0..1")
> I rather often use such configurations because it's an comfortable way to
> separate the service construction (via builder factory) from the service
> configuration (which is done at deployment time).
> So I improved builder factory. Now you can define configuration properties
> and parameters as typed configurations:
> For example, use:
> public void setConfiguration(Datum datum)
> {
> _datum = datum;
> }
> instead of:
> public void setConfiguration(List configuration)
> {
> _datum = (Datum) configuration.get(0);
> }
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
