Fixes are available
Rational Integration Tester 8.7
Rational Test Virtualization Server 8.7
Rational Performance Test Server 8.7
Rational Test Virtualization Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 4 (8.6.0.4) for 8.6
Rational Performance Test Server Fix Pack 4 (8.6.0.4) for 8.6
Rational Performance Test Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Integration Tester Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 3 (8.7.0.3) for 8.7
Rational Integration Tester Fix Pack 3 (8.7.0.3) for 8.7
Rational Performance Test Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 4 (8.7.0.4) for 8.7
Rational Test Virtualization Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Performance Test Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Test Virtualization Server Fix Pack 4 (8.6.0.4) for 8.6
Rational Performance Test Server Fix Pack 3 (8.7.0.3) for 8.7
APAR status
Closed as program error.
Error description
In some cases the validation of SOAP message fields gives incorrect failures and incorrect failure messages. For example you see this: Expected value "0.00", found value "{http://<namespace details>}0.00" (Action = "Equality") This field should have passed validation.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of Rational Integration Tester working with XML * * namespace identifier (Qname) validation. * **************************************************************** * PROBLEM DESCRIPTION: * * Prior to version 8.5.1, Rational Integration Tester * * performed XML namespace identifier (Qname) validation by * * comparing the values as strings. This meant that elements * * with different namespace names (that resolved to the same * * URL) would fail comparison when, logically, they were the * * same. For example, <ns1:customer> were not considered to be * * the same as <ns2:customer> when comparing expected and * * actual messages, even if the definitions of ns1 and ns2 * * resolved to the same URL. * * * * In release 8.5.1, this was changed so that comparison was * * done using the resolved namespace names. * * * * However, for some customers, this change introduced a * * problem in XML documents where the namespaces were not * * defined. In this case, Rational Integration Tester could * * not resolve the namespace identifier, and validation failed * * regardless of the string equivalence of the names. These * * users saw this problem as an undesired change in behavior. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
A fix for this issue was provided in version 8.7.0 of Rational Integration Tester, which now falls back to string comparison if the namespace identifier cannot be resolved for the XML messages. This preserves pre-8.5.1 behavior in these cases while still providing correct validation when the namespace is defined.
Temporary fix
Comments
APAR Information
APAR number
PI32902
Reported component name
RATL TEST WORKB
Reported component ID
5725G7900
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-01-16
Closed date
2015-05-20
Last modified date
2015-05-20
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 TEST WORKB
Fixed component ID
5725G7900
Applicable component levels
R800 PSY
UP
R801 PSY
UP
R850 PSY
UP
R851 PSN
UP
R860 PSN
UP
R870 PSY
UP
Document Information
Modified date:
17 October 2021