[
https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on WFLY-4444 at 3/19/15 7:00 AM:
----------------------------------------------------------------
My gut feeling is that the {noformat}${public.app.url}{noformat} reference in your wsdl is
actually not being resolved; instead, the JBossWS engine finds a soap:address location
that is not valid and hence performs address rewrite even if you disabled it (which is
correct, as the stack does not allow publishing wsdls with address that are not valid
urls). Can you try using a valid url there and see if anything changes?
was (Author: asoldano):
My gut feeling is that the ${public.app.url} reference in your wsdl is actually not being
resolved; instead, the JBossWS engine finds a soap:address location that is not valid and
hence performs address rewrite even if you disabled it (which is correct, as the stack
does not allow publishing wsdls with address that are not valid urls). Can you try using a
valid url there and see if anything changes?
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)