PQ98832: UNKNOWNHOSTEXCEPTION: SCHEMAS.XMLSOAP.ORG WSIF MUST USE A LOCAL COPY OF XSD FILE WHEN NO INTERNET CONNECTION IS AVAILABLE

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
6.0.1: WebSphere Application Server Version 6.0 Refresh Pack 1



APAR status
Closed as program error.

Error description
Currently, there is no setting to use a local copy of an XSD
file when that XSD file is declared to be located on the
internet. By specifying an import location on the internet, the
WSDL is explicitly saying to go get the XSD from the internet.
The WSIF runtime should have an option to use the local copy of
the file instead of looking the files on the internet.
Local fix
Test fix wsif.jar was provided to customer.
Problem summary
****************************************************************
* USERS AFFECTED: Users of WSIF with WSDL files which include  *
*                 XML Schema definitions from internet         *
*                 locations.                                   *
****************************************************************
* PROBLEM DESCRIPTION: If a WSDL file includes an XML Schema   *
*                      definition and specifies an internet    *
*                      location in the schemaLocation, WSIF    *
*                      will attempt to read the XSD document   *
*                      from that location. This is the case    *
*                      for XSD documents WSIF does not         *
*                      need such as common XSDs. For example,  *
*                      the WSDL XSD specification or the       *
*                      SOAP XSD specification.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a WSDL file includes an XML Schema definition using the
<import>, <include> or <redefine> XML Schema tags, these tags
may have an optional "schemaLocation" attribute. The value of
this attribute specifies where the XSD document is that contains
the Schema definition. Specifying this attribute tells the WSDL
processor (in this case WSIF and WSDL4J) where the Schema
document can be loaded from. For example:

<xsd:import
namespace="http://schemas.xmlsoap.org/wsdl/"
schemaLocation="http://schemas.xmlsoap.org/wsdl/"/>

In this scenario, the location of this document is an internet
location, specifically "http://schemas.xmlsoap.org/wsdl/".

Because "schemaLocation" is specified, WSIF will try to load
the document from the location specified. If there is no
internet connection available, an error message will be
produced with a "File not found" message.

The "schemaLocation" attribute is optional in the XSD
specification. If it is not specified, the XSD reader should
use its own internal version of the XSD, if available. WSIF
understands the SOAP and WSDL XSD and therefore does not need
schemaLocation to be specified for these XSD declarations:

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
Problem conclusion
WSIF has been changed to not attempt to load XSDs which
are located at http://schemas.xmlsoap.org. This includes
the common XSDs such as the WSDL or SOAP XSD.
The fix is targetted for WebSphere 5.1.1 cumulative
fix 4.
Please refer to the recommended updates page for delivery
information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PQ98832
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-12-22
Closed date 2005-03-08
Last modified date 2005-03-08

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSIF          

Publications Referenced

Fix information

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSN    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ98832
IBM Group: Software Group
Modified date: Mar 8, 2005