
Torsten,
Thanks for the quick fix. The index attributes now contain the correct enumerations. However, some index attributes now have invalid XML output. I have attached an example MIB along with the XSD output. It appears that the index element "vacmContextName" is printing out twice. The second occurance is nested within the first. In addition, only the root instance of this node has a closing attribute tag. Though, the fix is obviously not to start the second attribute from being added, so it doesn't really matter that it is an unterimated node.
I am using today's CVS tree.
Steve
-----Original Message----- From: Torsten Klie [mailto:tklie@ibr.cs.tu-bs.de] Sent: Friday, December 13, 2002 9:35 AM To: Steve Bucknam Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] xsd attribute output
Hi Steve!
On Fri, Dec 06, 2002 at 09:52:15AM -0500, Steve Bucknam wrote:
I have a table entry with an index that happens to be an enumeration. An excerpt from the mib follows. When I run smidump on the mib, the enumerations are lost. The generated type is "Enumeration". I would have expected there to be a Type of integer with an enumeration of restrictions just as if the index was any other element in the entry.
I assume this is either a bug or functionality that hasn't been completed. I would expect to see the restriction information in the XSD file. Am I wrong?
No, you are absolutely right. The code for index attributes was still missing. I have extended the corresponding code and commited it to the CVS.
Regards, Torsten

Hi Steve!
On Tue, Dec 17, 2002 at 11:10:28AM -0500, Steve Bucknam wrote:
Thanks for the quick fix. The index attributes now contain the correct enumerations. However, some index attributes now have invalid XML output. I have attached an example MIB along with the XSD output. It appears that the index element "vacmContextName" is printing out twice. The second occurance is nested within the first. In addition, only the root instance of this node has a closing attribute tag. Though, the fix is obviously not to start the second attribute from being added, so it doesn't really matter that it is an unterimated node.
I have fixed the bug. Just a missing "else" before an "if". Sometimes small words can be very important :-).
Regards Torsten
participants (2)
-
Steve Bucknam
-
Torsten Klie