Bug 1180206 - Unable to unset wsdl-port and wsdl-secure-port if wrong value is entered first
Summary: Unable to unset wsdl-port and wsdl-secure-port if wrong value is entered first
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: EAP 6.4.0
Assignee: Heiko Braun
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-08 15:51 UTC by Jan Blizňák
Modified: 2015-09-09 14:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
It is not possible to change values of WSDL attributes port and secure port back to `undefined` via console if they already have any value set. Input fields for these attributes currently allows only numeric values and don't handle empty string as `undefined`. Workaround: To unset these attributes, use one of the following commands in the management CLI: ---- /subsystem=webservices:undefine-attribute(name=wsdl-port) ---- or ---- /subsystem=webservices:undefine-attribute(name=wsdl-secure-port) ----
Clone Of:
Environment:
Last Closed: 2015-09-09 14:44:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-764 0 Major Resolved Unable to unset wsdl-port and wsdl-secure-port via console 2017-11-08 20:24:09 UTC

Description Jan Blizňák 2015-01-08 15:51:42 UTC 
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
Comment 1 Jan Blizňák 2015-01-08 16:02:21 UTC 
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
Comment 2 Pavel Jelinek 2015-01-09 07:49:44 UTC 
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)
Comment 7 Tomas Hofman 2015-07-21 08:29:24 UTC 
Upstream fixed: https://issues.jboss.org/browse/HAL-764
Comment 8 JBoss JIRA Server 2015-08-20 12:11:27 UTC 
Jan Kašík <jkasik> updated the status of jira HAL-764 to Reopened
Comment 9 JBoss JIRA Server 2015-08-26 07:39:31 UTC 
Tomas Hofman <thofman> updated the status of jira HAL-764 to Coding In Progress
Comment 10 JBoss JIRA Server 2015-09-03 08:39:24 UTC 
Tomas Hofman <thofman> updated the status of jira HAL-764 to Resolved
Comment 12 Tomas Hofman 2015-09-09 14:44:52 UTC 
No customer case, resolved upstream.
Note You need to log in before you can comment on or make changes to this bug.