Question
Self
DE
Last activity: 4 Apr 2016 9:54 EDT
parsing XML - processContents=lax
Hi,
I need some help in handling the processContents=lax in Pega. We are facing an issue with Parse XML when the XML contains nodes for which the XSD definition as processContents="lax". Please find below the definition
When the Metadata Accelerator is run to import this XSD, Pega generated the parse XML as shown below. There is an _any_ tag and the Node contains Element Substitution.
The XML returned by the service contains additional tags which I think need to fit in the _any_ and the parse XML is supposed to parse them.
We created properties manually in the class and added additional elements manually in the Pega generated parse XML to parse these fields but Pega is not parsing them. We have also tried defining the element names in Element Substitution area in the XML tab of the parse XML rule but did not work.
Could you please advise how to parse the elements coming in the XML which fall into processContents=lax category.
Regards,
Swaroop
Accepted Solution
Self
DE
Hi,
The issue got resolved after adding the child elements on the Parse XML. The initial issue was with XSI type and this is resolved.
Thank you for your inputs.
Regards,
Swaroop
Hi Swaroop, what is the pega version? It appears that there is a disconnect between XML schema and data. additional tags returned by service should have fit into one of those substitutions. if you could, update the XML schema with those additional elements and try reimporting into pega to have those missing rules created by wizard. Is this behavior working fine, if 'processContents' not present?
Self
DE
Hi Gopinathan,
The Pega version is 7.1.7. The importing and other properties are getting generated for all other elements in XSD except processContents=lax . The interface XSD definition has processContents=lax for specific element as below. The issue is with additional elements coming from interface XML. I updated the pega generated parse XML as shown below to accommodate the incoming additional XML elements. I am not sure why the updated Parse XML which I mentioned below is not working.
Kindly advise where I am missing.
XSD
<xs:complexType name="Rate">
<xs:choice>
<xs:sequence>
<xs:element name="Value" type="xs:string"/>
<xs:element name="RatingAttribute" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
Hi Gopinathan,
The Pega version is 7.1.7. The importing and other properties are getting generated for all other elements in XSD except processContents=lax . The interface XSD definition has processContents=lax for specific element as below. The issue is with additional elements coming from interface XML. I updated the pega generated parse XML as shown below to accommodate the incoming additional XML elements. I am not sure why the updated Parse XML which I mentioned below is not working.
Kindly advise where I am missing.
XSD
<xs:complexType name="Rate">
<xs:choice>
<xs:sequence>
<xs:element name="Value" type="xs:string"/>
<xs:element name="RatingAttribute" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
<xs:element name="ID" type="xs:string"/>
<xs:element name="Type" type="xs:string"/>
<xs:element name="Start_Date" type="xs:string"/>
<xs:element name="End_Date" type="xs:string"/>
<xs:sequence>
<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:sequence>
</xs:choice>
</xs:complexType>
Pega generated Parse XML
XML coming from interface
Changes done to Parse XML (added additional elements as per incoming XML)
Regards,
Swaroop
Hi Swaroop, I checked this use case locally & it works fine. below are the details.
XSD schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="person">
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
<xs:any namespace="###any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Updated the Parse-XML rule manually.
sample xml data to parse:
Hi Swaroop, I checked this use case locally & it works fine. below are the details.
XSD schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="person">
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
<xs:any namespace="###any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Updated the Parse-XML rule manually.
sample xml data to parse:
<person>
<firstname>Hege</firstname>
<lastname>Refsnes</lastname>
<children>
<childname>Cecilie</childname>
</children>
</person>
here is the output
Self
DE
Hi Gopinathan,
Please advise what all the changes done in the Pega generated Parse XML to accept the dynamic XML attributes ? Have you made any element substitutions or any additions/removal of nodes in parse xml?
Regards,
Swaroop
Accepted Solution
Self
DE
Hi,
The issue got resolved after adding the child elements on the Parse XML. The initial issue was with XSI type and this is resolved.
Thank you for your inputs.
Regards,
Swaroop