XSD vs Dingo
Although Dingo is inspired by JAXB, it is not identicle. In this first release, Dingo does not generate an ObjectFactory or the equivalent of JaxbContent. Although J2EE/J2SE uses the pattern of context lookup, it may not be applicable for .NET. The old method of looking up a service in windows used to be windows registry. At a high level both look similar, but context lookups in J2EE is dynamic, whereas windows registry is mostly static.
XSD provides several options for compiling a specific element, type or URI. Since Dingo generates one file per class, there isn't a pressing need to support those options. Once a GUI is written for Dingo, it will be easier to open a schema and compile the desired element(s) or type(s). Dingo is designed to be flexible and can be embedded within other applications.
|Copyright 2004 Peter Lin|