Question
Tata Consultancy Services
IN
Last activity: 1 Feb 2017 11:56 EST
updating an existing xsd components using Connector and Metadata import
Hi Team,
I am using connector and metadata wizard to connect with extenal application this application gave me a xsd and WSDL file separately . Using the wizard i have first imported the XSD componets > I have selected all the complex properties in the xsd and generated the rules with the base class as cc-Fw-int-SVS1-. I could see all the rules and properties are created in class(CC-FW-int-SVS-XSDComplextype) and ruleset version 01-25-01.
After this there was a change in service definition or xsd. So i re-imported the service definition with the same base class
cc-Fw-int-SVS1- and rulesetversion as 01-25-02. But this time new class was created (CC-FW-int-SVS-XSDComplextype2). can any one point me why it is happening. I believe now the existing class CC-FW-int-SVS-XSDComplextype should be overridden right ?
Please let me know how to handle this scenario.. I am using pega 7.1.8
Pegasystems Inc.
US
Hello, does the revised XSD contain the changes to 'XSDComplexType' element? ideally it should create the rules that represends the delta. if you could send both the xsds, that would help.
Tata Consultancy Services
IN
Thanks for the update GOPI . yes my revised XSD contains change to the existing 'XSDComplexType' element
Old XSD
<xs:element name="NotificationRq" type="lexns:NotificationRqType" />
<xs:complexType name="NotificationRqType">
<xs:sequence>
<xs:element ref="common:SourceSystemCd" />
<xs:element ref="ch:RequestHeader" minOccurs="0" />
<xs:element ref="common:Detail" minOccurs="0" />
</xs:sequence>
<xs:attribute ref="lexns:type" use="optional" />
<xs:anyAttribute namespace="##any" processContents="lax" />
</xs:complexType>
NEW XSD
<xs:element name="NotificationRq" type="lexns:NotificationRqType" />
Thanks for the update GOPI . yes my revised XSD contains change to the existing 'XSDComplexType' element
Old XSD
<xs:element name="NotificationRq" type="lexns:NotificationRqType" />
<xs:complexType name="NotificationRqType">
<xs:sequence>
<xs:element ref="common:SourceSystemCd" />
<xs:element ref="ch:RequestHeader" minOccurs="0" />
<xs:element ref="common:Detail" minOccurs="0" />
</xs:sequence>
<xs:attribute ref="lexns:type" use="optional" />
<xs:anyAttribute namespace="##any" processContents="lax" />
</xs:complexType>
NEW XSD
<xs:element name="NotificationRq" type="lexns:NotificationRqType" />
<xs:complexType name="NotificationRqType">
<xs:complexContent>
<xs:extension base="lexns:BaseNotificationType">
<xs:sequence>
<xs:element ref="common:OptionId" minOccurs="0"></xs:element>
<xs:element ref="common:NO_ID" minOccurs="0" />
<xs:element ref="lexns:Properties" minOccurs="0"></xs:element>
</xs:sequence>
<xs:attribute ref="lexns:type" use="optional" />
<xs:anyAttribute namespace="##any" processContents="lax" />
</xs:extension>
</xs:complexContent>
</xs:complexType>
Tata Consultancy Services
IN
Hi Gopi,
Can you please elobrate the behaviour, I am still unclear on how when same complextype is imported again it is creating new class rather than overwrite the existing class. Thanks in advance
Pegasystems Inc.
US
looks like definition of NotificationRqType element is changed between old and new XSD. wizard recognizes that new element is not the same element as exsisting, hence creating new one. also you observed that elements that did not change in new XSD is not created.
Tata Consultancy Services
IN
Hi Gopi,
Thanks for the response. I understand <xs:extension base> create a new direct inheritance. class inheritance this is being the reason for new class creation with suffix as 2. Please correct me if i am wrong.
There are lot of rules which are present in my old class. So to overcome this change I am doing below stuff. Please correct me if I am wrong. Thanks in advance
- Change the old Class Direct inheritance with class in <xs:extension base>
- Move the new properties and xml stream and parse xml of the new class (Created through wizard ) to old class
Pegasystems Inc.
US
Hello, after the import of the updated XSD, there should not be any extensive changes; it should work as it is. if you have to move the rules to new class means there is a problem. have you tried running the update wizard in steam/parse rule as mentioned by BinodG81?
if update wizard also did not work, this might need a further analysis of the update wizard/import wizard. please contact Pega support by creating a SR. please reference this thread for the context.