Fixes are available
APAR status
Closed as program error.
Error description
In the schema definition, if there are multiple sequences defined in a complex type, and if the same child element definition is used in more than one sequence definition, then the sequential elements in an XML document are reversed after deserializing or serializing in eager parsing mode.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: IBM Business Process Manager V7.5.1.1 * * Advanced and Express * **************************************************************** * PROBLEM DESCRIPTION: Within the mediation, XSD elements * * are getting swapped into the wrong * * sequence in eager parsing mode. This * * can occur if the same child element * * is used in more than one sequence. * * For example, in the following schema, * * the ¢â‚¬ “CommonLine ¢â‚¬ ½ element is * more * * than once: * * -------------------------------------- * * <complexType name="RootType"> * * <sequence> * * <element name="FirstElement" * * type="string"></element> * * <choice> * * <sequence> * * <element * * name="FirstChoiceLine1" * * type="string"/> * * <element name="CommonLine" * * type="string" /> * * </sequence> * * <sequence> * * <element * * name="SecondChoiceLine1" * * type="string"/> * * <element name="CommonLine" * * type="string" /> * * </sequence> * * </choice> * * <element name="LastElement" * * type="string"></element> * * </sequence> * * </complexType> * * -------------------------------------- * * This will cause the sequential * * elements in the XML document to be * * reversed after deserializing or * * serializing in eager parsing mode. * * For example, assume the following XML * * is based on the schema defined above: * * -------------------------------------- * * <?xml version="1.0" encoding="UTF-8"?> * * <RootElement * * xmlns="http://www.example.org/NewXMLSch * * ema" > * * <FirstElement>First * * Line</FirstElement> * * <SecondChoiceLine1>Line * * 1</SecondChoiceLine1> * * <CommonLine>Line 2</CommonLine> * * <LastElement>The End</LastElement> * * </RootElement> * * After deserializing and serializing, * * the XML will become: * * -------------------------------------- * * <?xml version="1.0" encoding="UTF-8"?> * * <RootElement * * xmlns="http://www.example.org/NewXMLSch * * ema"> * * <FirstElement>First * * Line</FirstElement> * * <CommonLine>Line 2</CommonLine> * * <SecondChoiceLine1>Line * * 1</SecondChoiceLine1> * * <LastElement>The End</LastElement> * * </RootElement> * * --------------------------------------- * * - * **************************************************************** * RECOMMENDATION: * **************************************************************** In the schema definition, if there are multiple sequences defined in a complex type, and if the same child element is used in more than one of the sequence definitions, the IBM BPM business object service will get the wrong structure feature for that child element due to the limitation of EMF (Eclipse Modeling Framework). This issue will cause the sequential elements in an XML document to be reversed after deserializing or serializing in eager parsing mode.
Problem conclusion
To prevent the sequential elements in an XML document from being reversed, apply the available fix for IBM Business Process Manager V7.5.1.1. To get the fix, go to Fix Central (http://www.ibm.com/support/fixcentral) and search for JR48969: 1. Select the product group, product, installed version, and platform, and click Continue. 2. Select APAR or SPR, enter JR48969, and click Continue. When downloading fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Comments
APAR Information
APAR number
JR48969
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-06
Closed date
2014-03-07
Last modified date
2014-03-07
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 October 2021