[
https://issues.jboss.org/browse/WFLY-6223?page=com.atlassian.jira.plugin....
]
Chao Wang edited comment on WFLY-6223 at 3/22/16 1:34 AM:
----------------------------------------------------------
This is not an issue in HAL as originally reported. When it writes the attributes in ws
provider form, it writes also attribute Wsdl host : ${jboss.bind.address:127.0.0.1} as
well, which requires a reload action if there is an active ws deployment. Because
WSServerConfigAttributeHandler compares unresolved current value to a resolved value. If
you click "Save" without changing any value, it asks for a server reload as
well.
was (Author: soul2zimate):
This is not an issue in HAL as originally reported. When it writes the attributes in ws
provider form, it write also attribute Wsdl host : ${jboss.bind.address:127.0.0.1} as
well, which requires a reload action if there is an active ws deployment. Because
WSServerConfigAttributeHandler compares unresolved current value to a resolved value. If
you click "Save" without changing any value, it asks for a server reload as
well.
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@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)