APAR status
Closed as program error.
Error description
When using the validate policy to validate an XML document against a definition containing an "allOf" property, the policy may return a failure and an error response of "Invalid XML payload received." even though the XML document correctly matches the definition.
Local fix
Problem summary
Despite having a valid XML document which matches a definition with an "allOf" property, the validation policy can fail to successfully validate the received XML document. A HTTP 400 or 422 status code with an error claiming an Invalid XML payload may be seen.
Problem conclusion
The fix is targeted for inclusion in v5.0.8.2 and an iFix following v5.0.6.5.
Temporary fix
Comments
APAR Information
APAR number
LI79929
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-07
Closed date
2018-01-05
Last modified date
2018-01-05
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
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0.0.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 September 2023