Bug 1031642 - WebServices subsystem attribute modify-wsdl-address false value ignored
Summary: WebServices subsystem attribute modify-wsdl-address false value ignored
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR0
: EAP 6.3.0
Assignee: Alessio Soldano
QA Contact: Rostislav Svoboda
Russell Dickenson
URL:
Whiteboard:
Depends On: 1061340
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 13:03 UTC by Petr Sakař
Modified: 2014-06-28 15:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previous versions of JBoss EAP 6 carried a bug that prevented the WS stack from processing @WebService(wsdlLocation=...) when performing wsdl soap:address rewrite. The annotation attribute above was not processed when the annotation was put on service endpoint interfaces only. This issue has been corrected in this release.
Clone Of:
Environment:
Last Closed: 2014-06-28 15:42:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
deployed war (5.01 KB, application/x-webarchive)
2013-11-18 13:03 UTC, Petr Sakař 		no flags Details
View All

Description Petr Sakař 2013-11-18 13:03:50 UTC 
Created attachment 825590 [details]
deployed war

Description of problem:

WSDL address in provided wsdl is modified even when attribute modify-wsdl-address of web services subsystem is set to false 

Version-Release number of selected component (if applicable):
EAP 6.2.0.ER7, 6.2.0.CR1, 6.2.0.CR2 

How reproducible:
always

Steps to Reproduce:
1. start AS
   bin/standalone.sh
2. change configuration
   bin/jboss-cli.sh -c "/subsystem=webservices/:write-attribute(name=modify-wsdl-address,value=false)"
3. reload AS
   bin/jboss-cli.sh -c "reload"
4. verify attribute value
   bin/jboss-cli.sh -c "/subsystem=webservices/:read-attribute(name=modify-wsdl-address)"
5. deploy war
   bin/jboss-cli.sh -c "deploy /tmp/CLIWebservicesModifyWsdlAddressTestCase.war" 
6. Check provided wsdl on address 
   http://localhost:8080/CLIWebservicesModifyWsdlAddressTestCase/AnnotatedSecurityService?wsdl


Actual results:
WSDL contains modified SOAP address
<soap:address location="http://localhost:8080/CLIWebservicesModifyWsdlAddressTestCase/AnnotatedSecurityService"/>

Expected results:
WSDL should contain unmodified SOAP address from deployed war from file META-INF/endpoint.wsdl
<soap:address location="http://localhost:8081/CLIWebservicesModifyWsdlAddressTestCase/AnnotatedSecurityService"/>



Additional info:
Comment 1 Alessio Soldano 2013-11-18 13:13:56 UTC 
The wsdl file contained in the deployment is not actually used for the org.jboss.test.ws.cli.AnnotatedServiceImpl endpoint.
Comment 2 Rostislav Svoboda 2013-11-18 14:29:18 UTC 
reproducer: https://github.com/psakar/eap-ws-management-tests
Comment 3 Alessio Soldano 2013-11-18 15:54:28 UTC 
As said on IRC, please disregard my former comment (#1) as it's based on wrong decompiled archive.
Comment 4 Alessio Soldano 2013-11-18 18:11:38 UTC 
This is caused by the bug here: https://issues.jboss.org/browse/JBWS-3736
Comment 5 Alessio Soldano 2013-11-18 18:13:06 UTC 
A workaround should be to simply move the wsdlLocation attribute from the @WebService annotation in the SEI to the one in the endpoint implementation.
Comment 6 Rostislav Svoboda 2013-11-19 07:47:27 UTC 
Lowering severity, we have workaround.
Comment 8 favrycio 2014-04-03 14:19:05 UTC 
This bug persist on wildfly
Comment 9 Alessio Soldano 2014-04-03 14:46:16 UTC 
favrycio, this has been fixed in https://issues.jboss.org/browse/JBWS-3736 , which is also included in JBossWS 4.2.4, which in turn will be in WildFly 8.0.1.
Comment 10 Kabir Khan 2014-04-04 14:55:16 UTC 
Setting to ON_QA since upgrade should fix this
Comment 11 Petr Sakař 2014-04-08 10:45:13 UTC 
Verified for EAP-6.3.0.ER1
Note You need to log in before you can comment on or make changes to this bug.