[jboss-jira] [JBoss JIRA] (WFLY-4444) Ability to set WSDL URL
Alessio Soldano (JIRA)
issues at jboss.org
Wed Mar 25 04:50:20 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053244#comment-13053244 ]
Alessio Soldano commented on WFLY-4444:
---------------------------------------
To use the jbossws-cxf.xml, you need to enable the Spring integration, which is not the suggested approach (and is being deprecated in next JBossWS 5).
As I previously said, I think at this point it would be great if you could provide me/us some kind of reproducer or a simplified version of you app that fails in your environment, so that we can take a look.
> 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)
More information about the jboss-jira
mailing list