[xsde-users] Q: Two delimiters with same name in a complex type

Rangarajan, Ravi_Sowmian raviraja at qti.qualcomm.com
Fri Jul 17 02:35:14 EDT 2015

Hi Boris,
Complex type below, reoccurrenceStartStopType, has to sv::delimiter in it. Use cases I am interested in are

Q1. After index, which is unsigned int type, we want to pack a delimiter, then I want to skip r11:receptionFiltering and r12:FDTInstanceURI fields and then pack r12:reoccurenceAndMonitoring type and another delimiter right after that. For e.g.

<sessionSchedule >
                <r12:recurrenceAndMonitoring mode="true">

        Q2. When reoccurenceAndMonitoring is not packed, then I would like to pack two delimiters back to back after index. For e.g.,

<sessionSchedule >

Auto generated code is such that it just packs as many delimiters as specified back to back - On the other hand, I am unable insert second delimiter of the same type & same name after packing ReoccurenceAndMonitoring field into sessionSchedule. Example 2 above can easily be achieved with current TBS implementation, whereas, example 1 is what I am asking this question for.

Any tricks on how to facilitate independently packing two deliimiters under ReoccurenceStartStopType, especially when ReoccurenceAndMonitoring needs to be packed?

Thanks in advance

### snippet from reference schema
<xs:complexType name="reoccurenceStartStopType">
                                                <xs:element name="start" type="xs:dateTime"/>
                                                <xs:element name="stop" type="xs:dateTime"/>
                                                <xs:element name="reoccurencePattern" type="xs:string" minOccurs="0"/>
                                                <xs:element name="numberOfTimes" type="xs:unsignedInt" minOccurs="0"/>
                                                <xs:element name="reoccurenceStopTime" type="xs:dateTime" minOccurs="0"/>
                                                <xs:element name="index" type="xs:unsignedInt" minOccurs="0"/>
                                                <xs:element ref="r11:receptionFiltering" minOccurs="0"/>
                                                <xs:element ref="sv:delimiter"/>
                                                <xs:element ref="r12:FDTInstanceURI" minOccurs="0"/>
                                                <xs:element ref="r12:recurrenceAndMonitoring" minOccurs="0"/>
                                                <xs:element ref="sv:delimiter"/>
                                                <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
                                <xs:attribute ref="r12:sessionDescriptionURI"/>
                                <xs:anyAttribute processContents="skip"/>

More information about the xsde-users mailing list