[jboss-jira] [JBoss JIRA] (WFLY-6223) Enabling statistics in web console requires reload while it doesn't in CLI

[Chao Wang (JIRA)]

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

Chao Wang moved JBEAP-3425 to WFLY-6223:
----------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-6223  (was: JBEAP-3425)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Web Console
                       Web Services
                           (was: Web Console)
       Target Release:   (was: 7.0.0.GA)
    Affects Version/s: 10.0.0.Final
                           (was: 7.0.0.ER5)


> Enabling statistics in web console requires reload while it doesn't in CLI
> --------------------------------------------------------------------------
>
>                 Key: WFLY-6223
>                 URL: https://issues.jboss.org/browse/WFLY-6223
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web Console, Web Services
>    Affects Versions: 10.0.0.Final
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>
> If I want to enable statistics for Web Services subsystem, I do it in CLI:
> {noformat}
> [standalone at localhost:9990 /] /subsystem=webservices:write-attribute(name=statistics-enabled, value=true)
> {"outcome" => "success"}
> {noformat}
> Via web console, I navigate to Configuration->Subsystems->Web Services->View
> I click edit and click checkbox for statistics enabled attribute. Now when I submit the value by clicking Save, dialog appears with reload require information.
> There is no need to require reload just for enabling statistics, by the way statistics are accessible even before reload (Runtime->Subsystems->Webservices and try to get wsdl for the web service for several times).
> Note: if there is no active deployment, reload is not required in web console (correct). To reproduce the issue you must have some active WS deployment



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)