Fix (APAR):  JR26916

Status:  Fix

Release:  6.0.2.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  31819

Date: 2007-07-12

Abstract:  CDATA elements cannot be used because the '>' character is not escaped properly.

Description/symptom of problem:  
JR26916 resolves the following problem:

ERROR DESCRIPTION:                                              
CDATA elements cannot be used because the '>' character is not  
escaped properly.                                               
                                                                
This is the same issue as JR26280, however this APAR is for     
Process Server 6.0.2.1                                          

LOCAL FIX:                                                      
manually escape the '>' character                               

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprize Service Bus 6.0.1.x and 6.0.2.x
users.

PROBLEM DESCRIPTION:
CDATA elements cannot be used because
the '>' character is not escaped
properly.


RECOMMENDATION:
None

CDATA elements passed within XML will result in Exception that
"]]>" is not found. <Created><![CDATA[aaaa]]></Created>
Users created with the XML elements are not working.

The exception:
org.xml.sax.SAXParseException: The character sequence "]]>"
must not appear in content unless used to mark the end of a
CDATA section.

at org.apache.xerces.util.ErrorHandlerWrapper.
createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.
fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError
Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError
(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError
(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.
scanContent(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$
FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.
scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse
(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse
(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse
(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse
(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load
(XMLLoadImpl.java:129)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad
(XMLResourceImpl.java:155)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
(ResourceImpl.java:895)

PROBLEM CONCLUSION:                                             
 The iFix can resolve the CDATA issue.                          


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server

Additional Information: