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.
Created attachment 825590 [details]
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
Steps to Reproduce:
1. start AS
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
WSDL contains modified SOAP address
WSDL should contain unmodified SOAP address from deployed war from file META-INF/endpoint.wsdl
The wsdl file contained in the deployment is not actually used for the org.jboss.test.ws.cli.AnnotatedServiceImpl endpoint.
As said on IRC, please disregard my former comment (#1) as it's based on wrong decompiled archive.
This is caused by the bug here: https://issues.jboss.org/browse/JBWS-3736
A workaround should be to simply move the wsdlLocation attribute from the @WebService annotation in the SEI to the one in the endpoint implementation.
Lowering severity, we have workaround.
This bug persist on wildfly
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.
Setting to ON_QA since upgrade should fix this
Verified for EAP-6.3.0.ER1