Fixes are available
Rational Software Architect Fix Pack 1 (9.0.0.1) for 9.0
Rational Software Architect for WebSphere Software Fix Pack 1 (9.0.0.1) for 9.0
Rational Software Architect Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Software Architect 9.1
Rational Software Architect for WebSphere Software 9.1
Rational Software Architect Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect 9.1.1
Rational Software Architect for WebSphere Software 9.1.1
Rational Software Architect Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Software Architect for WebSphere Software 9.1.2
Rational Software Architect 9.1.2
Rational Software Architect Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 1 (9.1.2.1) for 9.1.2
Rational Software Architect Fix Pack 2 (9.1.2.2) for 9.1.2
Rational Software Architect Fix Pack 3 (9.1.2.3) for 9.1.2
Rational Software Architect for WebSphere Software Fix Pack 1 (9.1.2.3) for 9.1.2
APAR status
Closed as program error.
Error description
Environment: Windows 7 Rational Software Architect 8.5.1 Reproducible: Yes Description of problem: In a UML model with documentation written in XML, when you run a UML->XSD transformation, the XML characters (such as '<' and '>') are escaped (into '<' and '>'). However this is contrary to the XSD specification (see http://www.w3.org/TR/xmlschema11-1/ Section A). Rational Software Architect should not be escaping XML caracters but rather validating the documentation section before generating the XSD files. Steps to reproduce: 1. Create a UML model with the 'XSD Transformation' profile. 2. Create a UML package with the 'Schema' stereotype. 3. Add XML documentation to it 4. Create a UML to XSD transformation for this model and run it. 5. Notice that in the generated XSD the XML characters of the documentation are escaped. Workaround: There is no known workaround.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** In a UML model with documentation written in XML, when you run a UML-to-XSD transformation, the XML characters (such as ")
Problem conclusion
The problem has been fixed to only encode HTML tags while any other custom XML tag entered in the documentation is retained as-is in the generated XML/WSDL file.
Temporary fix
Comments
APAR Information
APAR number
PM97519
Reported component name
RATL SW ARCHITE
Reported component ID
5725A3000
Reported release
851
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-20
Closed date
2014-06-13
Last modified date
2014-06-13
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 SW ARCHITE
Fixed component ID
5725A3000
Applicable component levels
R851 PSN
UP
Document Information
Modified date:
10 September 2020