[jboss-jira] [JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737453#comment-12737453 ] 

Brian Stansberry commented on AS7-5403:
---------------------------------------

I'm fine with removing the extra level of configuration if JFC is, although you'll still have to support the old mod-cluster-config=configuration child resource for backwards compatibility.

There is still the problem I mentioned above though re: the child resources under mod-cluster-config=configuration (DynamicLoadProviderDefinition, LoadMetricDefinition, CustomLoadMetricDefinition). If those resources are added after the initial add of the subsystem, and during boot, the result is the change isn't applied to the runtime and the server is put into reload-required. At a minimum we need to get it so if those are added after boot but as part of the same composite op that adds the subsystem, the reload isn't required. We can chat about how to do that. Ideally though some of those could be added at any time and the running service would be updated.

Using a default of 'modcluster' for advertise is ok, but only if you track whether or not the value was actually set in the config. IOW, "undefined" in the model leads to trying to use "modcluster" and disabling advertise if unsuccessful. But any specifically defined value has to be correct or it's a failure.
                
> CLONE - Adding modcluster via the CLI fails.
> --------------------------------------------
>
>                 Key: AS7-5403
>                 URL: https://issues.jboss.org/browse/AS7-5403
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Tom Fonteyne
>            Assignee: Joe Wertz
>             Fix For: 7.2.0.Alpha1
>
>
> Adding modcluster via the CLI fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira