Currently, XML for xmpp message doesn't support attribute declaration.
Example:
Mobility extended community needs two information. sequence number and sticky bit
In the current schema, this needs to be defined as two different element.
<xsd:element name="sequence-number" type="xsd:integer"/>
<xsd:element name="sticky" type="xsd:integer"/>
This will add two xml nodes to xmpp message making it more verbose and bulky
<xmpp-message>
<sequence-number> 1 </sequence-number>
<sticky> False </sticky>
</xmpp-message>
This xmpp message can be represented with one XML node with attributes.
<xmpp-message>
<mobility seqno="2" sticky="true" />
</xmpp-message>
Add support for XML attribute in schema and auto generation of types/parser code
Reviewed: https:/ /review. opencontrail. org/26963 github. org/Juniper/ contrail- generateDS/ commit/ 76e64fd3204aff4 33ad2383258e65e 62809ca41c
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 76e64fd3204aff4 33ad2383258e65e 62809ca41c
Author: Prakash Bailkeri <email address hidden>
Date: Wed Dec 7 22:26:48 2016 +0530
Support attribute for xmpp messaging
Currently, XML for xmpp message doesn't support attribute declaration.
Example: number" type="xsd: integer" /> integer" />
Mobility extended community needs two information. sequence number and sticky bit
In the current schema, this needs to be defined as two different element.
<xsd:element name="sequence-
<xsd:element name="sticky" type="xsd:
This will add two xml nodes to xmpp message making it more verbose and bulky
<xmpp-message>
<sequence-number> 1 </sequence-number>
<sticky> False </sticky>
</xmpp-message>
This xmpp message can be represented with one XML node with attributes.
<xmpp-message>
<mobility seqno="2" sticky="true" />
</xmpp-message>
Add support for XML attribute in schema and auto generation of types/parser code
Change-Id: Idbd238ec414f7b 18c897c8482cfdf f04c0f77876
Related-bug: #1645092