[
https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on WFLY-4444:
---------------------------------------
mmh... we do have a test that verifies the scenario with disabled address rewrite. Not
sure if you can provide me a sample app to reproduce your exact scenario (app + wfly conf,
the only missing element being the load balancer). Btw, which exact soap address location
have you actually written in the wsdl this time?
Perhaps you can get the JBossWS 4.3.2.Final sources, attach a debugger there and step
through MetadataBuilder#processAddressRewrite method [1] to see why the address is being
rewritten?
[1]
http://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.2.F...
Ability to set WSDL URL
-----------------------
Key: WFLY-4444
URL:
https://issues.jboss.org/browse/WFLY-4444
Project: WildFly
Issue Type: Feature Request
Components: Web Services
Affects Versions: 8.2.0.Final
Reporter: John Ament
Assignee: Alessio Soldano
There's no way to correctly set a WSDL URL. The properties are:
{code}
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>${public.app.host:localhost}</wsdl-host>
<wsdl-port>${public.http.port:80}</wsdl-port>
<wsdl-secure-port>${public.https.port:443}</wsdl-secure-port>
{code}
We need a way to set the WSDL URL, regardless of the protocol used. The issue being that
our app servers run on HTTP, but the incoming request to the first load balancer is over
HTTPS. The result is that the WSDL generated includes
http://public-host:80/ instead of
https://public-host:443/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)