]
Alessio Soldano updated JBWS-2771:
----------------------------------
Fix Version/s: jbossws-native-3.3
Priority: Major (was: Critical)
Importes XSD´s schemaLocation URL Port not changed when
"webServicePort" property set in stack-agnostic-jboss-beans.xml
-----------------------------------------------------------------------------------------------------------------------
Key: JBWS-2771
URL:
https://jira.jboss.org/jira/browse/JBWS-2771
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.0
Environment: Debian, JDK 1.6.0-13, JBoss 5.1 with Patched JBossWS 3.2.0 Native
(Patched means
https://jira.jboss.org/jira/browse/JBWS-2759). Also in WinXP
Reporter: David Calvente
Assignee: Alessio Soldano
Fix For: jbossws-native-3.3
In an environtment where JBoss 5.1 is behind an Apache ReverseProxy, JBoss running on
port 8080, but accessed via reverse proxy via port 80, you can use
stack-agnostic-jboss-beans.xml to modify:
host name:
<property
name="webServiceHost">jbossws.undefined.host</property>
<property name="modifySOAPAddress">true</property>
and Port:
<property name="webServicePort">80</property>
This works OK for endPoint:
<soap:address location="http://server.domain.com:80/typex/ws"/> Uses Port
80 as specified!!
BUT leaves unmodified Port for schemaLocation:
"http://server.domain.com:8080/typex/ws?wsdl&resource=TXM_Fault.xsd"/>
Uses JBoss port and NOT 80 !!!
So, when a client tries to use the WSDL it can't find the referenced XSD's
failing!!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: