[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-283) Refactor ModClusterConfig to allow complex types

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-283.
-------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> Refactor ModClusterConfig to allow complex types
> ------------------------------------------------
>
>                 Key: MODCLUSTER-283
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-283
>             Project: mod_cluster
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 1.2.1.Beta2
>
>
> mod_cluster's configuration interfaces were originally designed to accept simple configuration property values.  With AS7, complex property types (e.g. InetAddress, Collection<InetSocketAddress>, Set<String>) are easier to define - and the old methods are now cumbersome.  We should keep the old mutator methods (for backwards compatibility), but alter the accessor methods to accept more complex types.
> e.g.
> Collection<InetSocketAddress> MCMPConfiguration.getProxies();
> void ModClusterConfig.setProxies(Collection<InetSocketAddress>);
> void ModClusterConfig.setProxyList(String proxyList);
> InetAddress AdvertiseConfiguration.getAdvertiseGroupAddress();
> void ModClusterConfig.setProxies(Collection<InetSocketAddress>);
> void ModClusterConfig.setProxyList(String proxyList);
> etc.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)