Finan
12 years agoFrequent Contributor
unable to handle redirected wsdl
situation:
JAXWS Webservice, deployed on WAS 7. Webservice points to packaged WSDL, thus when requesting the WSDL using:
context-root/GetCustomerData?wsdl
you will be redirected to :
context-root/GetCustomerData/WEB-INF/wsdl/CustomerDataService.wsdl
This redirect is automatically performed by WebSphere when you supply a location for your WSDL in your annotated service.
Unfortunately, when using the first URL when loading a new soap project based on a WSDL, Soap UI (pro, 4.6.1) fails to load any .xsd references present in the WSDL, because it tries to resolve the xsd relative to entered url, instead of the url WebSphere redirects to.
By entering the second url, it does work.
JAXWS Webservice, deployed on WAS 7. Webservice points to packaged WSDL, thus when requesting the WSDL using:
context-root/GetCustomerData?wsdl
you will be redirected to :
context-root/GetCustomerData/WEB-INF/wsdl/CustomerDataService.wsdl
This redirect is automatically performed by WebSphere when you supply a location for your WSDL in your annotated service.
Unfortunately, when using the first URL when loading a new soap project based on a WSDL, Soap UI (pro, 4.6.1) fails to load any .xsd references present in the WSDL, because it tries to resolve the xsd relative to entered url, instead of the url WebSphere redirects to.
By entering the second url, it does work.