PQ78920: Relative links in WSDL files fail to import | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description WDSL files which link to each other with just the file name and not the absolute address, fail to load with the following error: WSDLException (at /definitions/import): faultCode=OTHER_ERROR: Unable to locate imported document at ''<short name>.wsdl'', relative to ...Local fix A suggested workaround is to not specify a Classloader in the getService() method call on WSIFServiceFactory in the WebServices clients. Replace: WSIFServiceFactory.getService(java.lang.String wsdlLoc, java.lang.ClassLoader cl, java.lang.String serviceNS, java.lang.String serviceName, java.lang.String portTypeNS, java.lang.String portTypeName) with: WSIFServiceFactory.getService(java.lang.String wsdlLoc, java.lang.String serviceNS, java.lang.String serviceName, java.lang.String portTypeNS, java.lang.String portTypeName)Problem summary **************************************************************** * USERS AFFECTED: Users of WebSphere Application Server who * * use WSIF to invoke services with relative * * imports defined in their WSDLs and specify * * a ClassLoader to locate WSDL files. * **************************************************************** * PROBLEM DESCRIPTION: When a Web Services client in * * WebSphere uses WSIF, specifies a * * ClassLoader to WSIF and tries to load * * a WSDL file which uses a relative * * import, WSIF throws a WSIFException. * * The WSIFException reports WSIF cannot * * locate the imported document * * specified in the WSDL file. * **************************************************************** * RECOMMENDATION: * **************************************************************** WSIF reports an error when trying to resolve an imported WSDL definition file using a relative import and when running WebSphere Application Server V5.0.2.Problem conclusion Temporary fix Comments This APAR is being closed FIN with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release which is being developed at the time that the APAR was closed. The latest release of the product to exit development at the time this APAR was closed was: WebSphere Application Server 5.0.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ78920
IBM Group: Software Group
Modified date: Dec 16, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.