[
https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JBWS-3569:
-----------------------------------------------
claprun(a)redhat.com made a comment on [bug
880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729]
Note that applying the change to wsdl-host only seems to work *when* the JBoss WS patch
has been applied. It seems that using a non-patched JBoss WS version results in WSRP not
working at all in clustered or single-node mode since the port URLs use
jbossws.undefined.host instead of localhost in that case and are not being rewritten.
WSDL produced for a multi-port service contains invalid port
addresses in clustered configuration
-------------------------------------------------------------------------------------------------
Key: JBWS-3569
URL:
https://issues.jboss.org/browse/JBWS-3569
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Chris Laprun
Assignee: Alessio Soldano
Priority: Critical
Fix For: jbossws-cxf-4.1.1
Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in
ports containing the node URLs instead of the loadbalancer's.
I've tried using the dynamic WSDL rewriting as described in
https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid
URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster
node port) that haven't been used to access the WSDL, the port used to access the WSDL
has the proper address though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira