[
https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-5403:
----------------------------------------------
Tomaz Cerar <tcerar(a)redhat.com> made a comment on [bug
900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801]
What should be accepted solution to this?
Given that composite operation (cli batch) works as expected and verified?
In EAP 6.0.x modcluster:add() operation also did not expect or take any attributes:
output of operation definition in EAP 6.0.0.GA
[standalone@localhost:9999 subsystem=modcluster] :read-operation-description(name=add)
{
"outcome" => "success",
"result" => {
"operation-name" => "add",
"description" => "Operation adding the modcluster
subsystem.",
"request-properties" => {},
"reply-properties" => {},
"read-only" => false
}
}
Said this, I see no need to add new feature such as adding convenience attribute to
subsystem=modcluster:add this late in development stage.
I could be nice RFE for 6.2 but absolutely not for 6.1 as it would require lots of
additional work (model version upgrade, transformers, additional testing)
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, Clustering
Affects Versions: 7.1.2.Final (EAP)
Reporter: Tom Fonteyne
Assignee: Radoslav Husar
Fix For: 8.0.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