Fixes are available
APAR status
Closed as program error.
Error description
During application deployment copies are made of XML deployment descriptors. The current strategy rewrites these files, introducing changes. The save should preserve the original contents of the files.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Deployments rewrite deployment * * descriptors, introducing formatting * * changes. * **************************************************************** * RECOMMENDATION: * **************************************************************** When deploying an application, a step of deployment processing is a write of the application files to an installed applications location. That write includes a step where the deployment descriptors of the application are written. Current processing can rewrite deployment descriptors, even when no change has been made to the descriptors. For application client JAR files and EJB JAR files, this will usually change the signature of the JAR file, creating a problem for JAR verification tools which rely on signature information. The rewrite also changes the encoding of XML special characters, for example, changing "&" to "&apos". While this is valid and equivalent as XML text, the change can cause problems for tools which rely on the "&" character representation.
Problem conclusion
A code update was made to prevent unnecessary rewrites of deployment descriptors during application deployment. That enables the write of the initial application client JAR or EJB JAR, preserving the JAR signature. In additional XML special characters are left as original encoded. Use of this fix requires that impacted applications be redeployed. Note that the fix will not be effective if changes are required to be made to a deployment descriptor during application deployment. For example, if EJB method information is not complete prior to deployment, an update will be made to the EJB deployment descriptor, "ejb-jar.xml", and both signature information and XML special characters will still be effective. When EJB method elements are incomplete, steps must be taken prior to application deployment to complete the EJB method information. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.43. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 This APAR is a backport of APAR PM60915, which was integrated into IBM WebSphere Application Server v8.0.0.4. This current APAR PI63953 integrates the same changes to v7.0 service packs, and introduces no additional changes to service packs for v8.0 (or higher).
Temporary fix
Comments
APAR Information
APAR number
PI63953
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-09
Closed date
2016-11-29
Last modified date
2016-11-29
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 October 2021