| Groups | Blog | Home |
dotnet xml : xsd.exe cannot generate schema
stage a cs class. The xml file has a mix of defined namespaces and also an empty namespace. These are defined as follows: <silcn:silcn xmlns:silcn='http://silcn.org/200309' xmlns='http://xmlprobe.com/200312'> it contains an element <report> off the root and also a separate <Silcn:report> again off the root. When running xsd from the command line on the xml file it fails and returns an Error Message as follows: A DataTable named 'report' already belongs to this DataSet. Why can xsd not tell the difference between <report> and <Silcn:report> when they are clearly different? cheers --
Correct, xsd.exe cannot generate (infer) a schema from such an xml file.
But it is pretty simple to do it yourself. For example, write the XSD like so: ---- Begin Silcn.xsd ---- <xs:schema targetNamespace="http://silcn.org/200309" xmlns="http://silcn.org/200309" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://xmlprobe.com/200312" attributeFormDefault="qualified" elementFormDefault="qualified" [quoted text, click to view] > <xs:import namespace="http://xmlprobe.com/200312" schemaLocation="XmlProbeReport.xsd" /> <xs:element name="silcn"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:report" minOccurs="0" /> <xs:element ref="report" minOccurs="0" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="report" type="xs:string" /> </xs:schema> ---- End Silcn.xsd ---- ---- Begin XmlProbeReport.xsd ---- <xs:schema targetNamespace="http://xmlprobe.com/200312" xmlns="http://xmlprobe.com/200312" xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" [quoted text, click to view] > <xs:element name="report" type="xs:string" /> </xs:schema> ---- End XmlProbeReport.xsd ---- Then, if you run xsd.exe to generate classes like so: xsd.exe /c Silcn.xsd XmlProbeReport.xsd you will get something like this: ---- Begin generated class ---- [System.Xml.Serialization.XmlTypeAttribute(Namespace="http://silcn.org/200309")] [System.Xml.Serialization.XmlRootAttribute(Namespace="http://silcn.org/200309", IsNullable=false)] public class silcn { [System.Xml.Serialization.XmlElementAttribute(Namespace="http://xmlprobe.com/200312")] public string report; [System.Xml.Serialization.XmlElementAttribute("report")] public string report1; } ---- End generated class ---- Some people find it simpler to go in the other direction - start with C# and then generate XSD from it. To do this, write the C# (or VB) code similar to the above, attributed with the proper namespaces and so on. Then compile into an assembly (exe or DLL). Then do: xsd /type:silcn <assembly> ...This will give you 2 xsd files, corresponding to what I provided above. You can then round-trip, working in C# or VB and generating XSD, then tweaking XSD and re-generating C# or VB. If you have a test driver, you can verify that the C# code can actually de-serialize from a sample XML stream. Eventually you will get to the right schema and class. It is only in the inferring of the initial schema from an XML document, that the obstacle arises. If you skip that step, you should be on your way. I know this example is probably much simpler than what you need, but you should be able to follow the solution pattern for larger, more complex schema. -Dino ..NET Developer Group d i n o c h / online . m i c r o s o f t . c o m [quoted text, click to view] "PeterW" <nspw@noemail.nospam> wrote in message news:D195D944-7A79-4CBE-8B2D-5BA0039CF28D@microsoft.com... >I have an xml file from which I want to generate an xsd schema and at a >later > stage a cs class. > > The xml file has a mix of defined namespaces and also an empty namespace. > These are defined as follows: > <silcn:silcn xmlns:silcn='http://silcn.org/200309' > xmlns='http://xmlprobe.com/200312'> > > it contains an element <report> off the root and also a separate > <Silcn:report> again off the root. > > When running xsd from the command line on the xml file it fails and > returns > an Error Message as follows: > A DataTable named 'report' already belongs to this DataSet. > > Why can xsd not tell the difference between <report> and <Silcn:report> > when > they are clearly different? > > cheers > -- > PeterW
I had gone down the route of constructing xsds myself before I posted the
question. You did show me how to fix some things I got wrong. I resorted to updating the incoming xml files with a transformation as a kludge and then extracting a schema which is not a preferred option when updating Vocabularies and Policies. The original question is still valid however, being if a namespace is defined and is not qualified with a prefix, it should apply to all unqualified elements in the file by default as I understand it. I would have thought it should be dealt with by default by any schema inferencing tool such as xsd.exe. I would still like to understand why it is not as a matter of interest rather than to fix a problem. The reason I ask is that BizTalk makes a lot of use of xsd schemas. Maintaining such systems should be as easy as possible and if possible be able to be done by non programmers. The harder it is to create schemas the more of a maintainability nightmare there is with evolving business rules using tools such as the Business Rule Composer as business changes over time. If that is not the case then instead of making reliance on skills less over time the converse is true. You can see where I am going. cheers -- PeterW [quoted text, click to view] "DC" wrote:
> Correct, xsd.exe cannot generate (infer) a schema from such an xml file. > But it is pretty simple to do it yourself. For example, write the XSD like > so: > > ---- Begin Silcn.xsd ---- > > <xs:schema > targetNamespace="http://silcn.org/200309" > xmlns="http://silcn.org/200309" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns:ns1="http://xmlprobe.com/200312" > attributeFormDefault="qualified" > elementFormDefault="qualified" > > > > <xs:import namespace="http://xmlprobe.com/200312" > schemaLocation="XmlProbeReport.xsd" /> > > <xs:element name="silcn"> > <xs:complexType> > <xs:sequence> > <xs:element ref="ns1:report" minOccurs="0" /> > <xs:element ref="report" minOccurs="0" /> > </xs:sequence> > </xs:complexType> > </xs:element> > > <xs:element name="report" type="xs:string" /> > > </xs:schema> > > ---- End Silcn.xsd ---- > > > ---- Begin XmlProbeReport.xsd ---- > <xs:schema > targetNamespace="http://xmlprobe.com/200312" > xmlns="http://xmlprobe.com/200312" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > attributeFormDefault="qualified" > elementFormDefault="qualified" > > > > <xs:element name="report" type="xs:string" /> > > </xs:schema> > ---- End XmlProbeReport.xsd ---- > > > Then, if you run xsd.exe to generate classes like so: > > xsd.exe /c Silcn.xsd XmlProbeReport.xsd > > you will get something like this: > > ---- Begin generated class ---- > > [System.Xml.Serialization.XmlTypeAttribute(Namespace="http://silcn.org/200309")] > [System.Xml.Serialization.XmlRootAttribute(Namespace="http://silcn.org/200309", > IsNullable=false)] > public class silcn { > > [System.Xml.Serialization.XmlElementAttribute(Namespace="http://xmlprobe.com/200312")] > public string report; > > [System.Xml.Serialization.XmlElementAttribute("report")] > public string report1; > } > > ---- End generated class ---- > > > Some people find it simpler to go in the other direction - start with C# and > then generate XSD from it. To do this, write the C# (or VB) code similar > to the above, attributed with the proper namespaces and so on. Then compile > into an assembly (exe or DLL). Then do: > > xsd /type:silcn <assembly> > > ...This will give you 2 xsd files, corresponding to what I provided above. > > You can then round-trip, working in C# or VB and generating XSD, then > tweaking XSD and re-generating C# or VB. If you have a test driver, you > can verify that the C# code can actually de-serialize from a sample XML > stream. Eventually you will get to the right schema and class. > > It is only in the inferring of the initial schema from an XML document, that > the obstacle arises. If you skip that step, you should be on your way. I > know this example is probably much simpler than what you need, but you > should be able to follow the solution pattern for larger, more complex > schema. > > -Dino > ..NET Developer Group > d i n o c h / online . m i c r o s o f t . c o m > > > > > > "PeterW" <nspw@noemail.nospam> wrote in message > news:D195D944-7A79-4CBE-8B2D-5BA0039CF28D@microsoft.com... > >I have an xml file from which I want to generate an xsd schema and at a > >later > > stage a cs class. > > > > The xml file has a mix of defined namespaces and also an empty namespace. > > These are defined as follows: > > <silcn:silcn xmlns:silcn='http://silcn.org/200309' > > xmlns='http://xmlprobe.com/200312'> > > > > it contains an element <report> off the root and also a separate > > <Silcn:report> again off the root. > > > > When running xsd from the command line on the xml file it fails and > > returns > > an Error Message as follows: > > A DataTable named 'report' already belongs to this DataSet. > > > > Why can xsd not tell the difference between <report> and <Silcn:report> > > when > > they are clearly different? > > > > cheers > > -- > > PeterW > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |