
Is DEFVAL supported in smidump with xsd format? I have many defvals defined for different syntax types. The default values do not show up in the xsd output (at least, not in a way that is obvious to me). For example:
tsPartnerImportInitiate OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "initiate the import operation for this tsPartner." DEFVAL { false } ::= { tsPartnerEntry 4 }
Results in XSD output of:
<xsd:element name="tsPartnerImportInitiate" minOccurs="0"> xsd:annotation xsd:appinfo <maxAccess>read-write</maxAccess> <oid>1.3.6.1.4.1.2500.1.1.8.1.2.1.1.4</oid> <status>current</status> </xsd:appinfo> xsd:documentation initiate the import operation for this tsPartner. </xsd:documentation> </xsd:annotation> xsd:simpleType <xsd:restriction base="xsd:NMTOKEN"> <xsd:enumeration value="true"> xsd:annotation xsd:appinfo <intVal>1</intVal> </xsd:appinfo> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="false"> xsd:annotation xsd:appinfo <intVal>2</intVal> </xsd:appinfo> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleType> </xsd:element>

Hi!
Steve> Is DEFVAL supported in smidump with xsd format? I have many Steve> defvals defined for different syntax types. The default values Steve> do not show up in the xsd output (at least, not in a way that Steve> is obvious to me).
Ack. We'll have to add a <default> element to the <appinfo> element in those cases. Thanks for this hint.
-frank
participants (2)
-
Frank Strauss
-
Steve Bucknam