[
https://issues.jboss.org/browse/JBWS-3856?page=com.atlassian.jira.plugin....
]
Frank Cornelis commented on JBWS-3856:
--------------------------------------
The weird thing is that the xs:import schemaLocations are correct. But the soap:address
location is not.
For WS-MEX there is also more to it than just the WSDL location replacements.
For MetadataSections with Dialect
http://www.w3.org/2001/XMLSchema and some Location
element, the value of the Location element should also be adopted.
jbossws.undefined.host in WS-MEX WSDL metadata
----------------------------------------------
Key: JBWS-3856
URL:
https://issues.jboss.org/browse/JBWS-3856
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.3
Reporter: Frank Cornelis
When defining <wsdl-host>jbossws.undefined.host</wsdl-host> the JBoss CXF
indeed replaces the wsoap12:address location within the WSDL with the actual address. But
the same substitution is not applied on the WSDL within WS-MEX metadata. Seems like the
location is being replaced with an address containing jbossws.undefined.host, instead of
the actual host. This causes STS implementations that also expose MEX to fail.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)