[
https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin....
]
John Ament commented on WFLY-4444:
----------------------------------
Yep, sorry. I started down a path trying to figure out what was going on. You can see
the project here:
https://github.com/johnament/simple-ws
Here's where I'm at (to clarify why i was looking at jbossws-cxf.xml):
- Able to overwrite in the wsdl the direct host (even using variables doesn't work,
e.g. {{#@something@}}
- It seems that when I introduce Policy, the WSDL is always rewritten. I have to tinker
with that some more.
In the example, I have a local dns entry for spartalnx, my internal machine name.
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)