[jboss-jira] [JBoss JIRA] (WFLY-4444) Ability to set WSDL URL
[
https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin....
]
John Ament edited comment on WFLY-4444 at 3/25/15 10:16 AM:
------------------------------------------------------------
What does undertow have to do with this? This is pure HTTP.
So I can confirm that I get better results/control over the generated WSDL when I remove
Policy and EndpointConfig, which doesn't help as that will turn off security options,
but it avoids the extra overwrite of the WSDL. It still doesn't help me as I
can't get it to use a hardcoded HTTPS protocol.
was (Author: meetoblivion):
What does undertow have to do with this? This is pure HTTP.
So I can confirm that I get better results/control over the generated WSDL when I remove
Policy and EndpointConfig, which doesn't help as that will turn off security options,
but it avoids the extra overwrite of the WSDL. It still doesn't help me as I
can't get use a hardcoded HTTPS protocol.
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)