Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
A JAX-RPC Web service created using WSAD5.1.2 with WebSphere Application Server V5.1 runs correctly when run on WebSphere Application Server V5.1. However when the application is deployed on a later version of WebSphere Application Server (for example 7.0.0.13), the application may fail due to problems with the xsd:date and xsd:datetime values. This problem will only occur if the WSDL file contains elements that extend the xsd:date or xsd:datetime elements. This is an uncommon scenario.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 * * administrators migrating JAX-RPC * * applications from WebSphere Application * * Server V5.1. * **************************************************************** * PROBLEM DESCRIPTION: A JAX-RPC Web service from V5.1 may * * fail when deployed in later versions * * due to xsd:datetime and xsd:date xml * * values. * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR. * **************************************************************** A JAX-RPC Web service created using WSAD 5.1.2 with WebSphere Application Server V5.1 runs correctly when run on WebSphere Application Server V5.1. However when the application is deployed on a later version of WebSphere Application Server (example 7.0.0.13), the application may fail due to problems with the xsd:date and xsd:datetime values. This problem will only occur if the WSDL file contains elements that extend the xsd:date or xsd:datetime elements. This is an uncommon scenario. WebSphere Application Server Version 5.1 conforms to the JAX-RPC 1.0 Specification. Later versions of WebSphere Application Server conform to the JAX-RPC 1.1 Specification. The Java mapping associated with the extension of simpleTypes changed between these two specifications. Thus this problem will only occur if the JAX-RPC application was developed in WebSphere Application Server V5.1.
Problem conclusion
The JAX-RPC runtime is designed to accommodate both JAX-RPC 1.0 and JAX-RPC 1.1 applications. However in this particular scenario, the JAX-RPC runtime failed to locate and use the existing makeString and makeValue methods necessary to correctly serialize and deserialize the xsd:date and xsd:datetime values. In addition, if the JAX-RPC application is redeployed (using the wsdeploy tool), the makeString and makeValue methods may be incorrectly removed. The JAX-RPC runtime is changed to detect and use the makeString and makeValue methods. The result is the correct serialization and deserialization of the xsd:date and xsd:datetime values. The JAX-RPC wsdeploy code is changed to correctly generate the makeString and makeValue methods when a WebSphere Application Server V5.1 JAX-RPC application is deployed. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.37 and 7.0.0.17. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM26530
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-11
Closed date
2010-11-22
Last modified date
2010-11-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
27 October 2021