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

Tue Nov 27 12:53:21 EST 2012

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

Radoslav Husar commented on AS7-5403:
-------------------------------------

@[~brian.stansberry] No, I haven't seen it yet (since Joe didn't follow the Jira process and like the PR, nor does the commit itself reference this Jira...).

I don't like this approach though (though for 7.1.x as workaround why not). By what I have done locally so far, as part of AS7-3623, removing the extra level of configuration and just leveraging GenericSubsystemDescribeHandler which enables you to add properties as parameters -- I like this very much. 

I am wondering now though, what is the best approach with requiring advertise. The goal is to provide users with best default configuration so we need to make sure that advertise is on by default. However, that means that users either need to specifi advertise-socket or disable advertise when adding the subsystem. How about: make the socket default to 'modcluster' abd if its defined just go with it, otherwise just disable advertise if its not.. 

PS: 4 comments above, the advertise-socket should be modcluster, not ajp.

> 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