Description of problem: location: Runtime -> Subsystems -> Web -> Web Services When you set invalid value for wsdl-(secure-)port and try to save the change, red warning shows up. But then you are unable to unset this value (aka leave the field empty), with red warning showed you can only enter correct value and save. Version-Release number of selected component (if applicable): HAL version: 2.5.1.redhat-1 How reproducible: always Steps to Reproduce: 1. go to the location Runtime -> Subsystems -> Web -> Web Services 2. click edit 3. enter wrong value to WSDL secure port (letters or numbers<1) and try to save (red warnig should occur) 4. erase that value and try to save --> NO ACTION Actual results: nothing happens, red warning is still showed Expected results: new (empty) value is saved is successfully Additional info: WSDL Secure Port in description above is used because it is by default unset. similar scenario is working - when you try to unset WSDL port (which is by default set to 8080) 1. go to the location Runtime -> Subsystems -> Web -> Web Services 2. click edit 3. erase value of WSDL Port and try to save --> SUCCESS
Actually you can't unset the value of wsdl port or wsdl secure port at all if it has some value set already. Try this: 1. go to the location Runtime -> Subsystems -> Web -> Web Services 2. click edit 3. enter valid value to WSDL secure port (ie 8888) and save 4. click edit 4. erase that value and try to save --> red warning, unable to save Changing severity to urgent, because you are unable to get back to default configuration once you set value for port or secure port
Use Configuration -> instead of Runtime -> . There is no possibility to undefine these attributes in management console now. In CLI you can perform /subsystem=webservices:undefine-attribute(name=wsdl-port)
Upstream fixed: https://issues.jboss.org/browse/HAL-764
Jan Kašík <jkasik> updated the status of jira HAL-764 to Reopened
Tomas Hofman <thofman> updated the status of jira HAL-764 to Coding In Progress
Tomas Hofman <thofman> updated the status of jira HAL-764 to Resolved
No customer case, resolved upstream.