Fixes are available
APAR status
Closed as program error.
Error description
Environment: - Windows XP - Rational Application Developer v 70010 Reproducible Y/N: Y Description of problem: When opening an incorrect XSL file the CPU goes up to 100% and the JVM allocates more memory all the time until it crashes. example code can be : <--xsl:template match='*[local-name(.)='GmfHeader']'> <-- xsl:template match='//GmfHeader' --> <--xsl:element name='GmfHeader' namespace='http:\\some.namespace.com' > <--xsl:apply-templates/> <--/xsl:element> <--/xsl:template> Step to reproduce: Workaround:
Local fix
Problem summary
The parser utilized by the XSL validator continues to operate even when fatal errors are encountered. Depending on the type of error, this can potentially lead to process failure.
Problem conclusion
The parser utilized by the XSL validator is modified to stop whenever a fatal error is encountered, adding robustness to the process.
Temporary fix
Comments
APAR Information
APAR number
PM11919
Reported component name
RATL APP DEV WI
Reported component ID
5724J1901
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-09
Closed date
2010-06-18
Last modified date
2010-06-18
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
RATL APP DEV WI
Fixed component ID
5724J1901
Applicable component levels
R700 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
18 June 2010