|
Take a look at System.Data.DataSet.ReadXml(...) and then binding the appropriate tables to the DataGridView object.
|
|
|
|
|
Hello,
Many thanks for you reply  I managed to display the extracted element (addresses) in DataGridView (binded to dataset that contains <ADDRESSES>) fine, but could not figure out a way to update the original xml file if the dataGrid is updated.
For example, I have the following in "addressTry.xml" :
<MEMBER>
<GENDER>FEMALE</GENDER>
<AGE>35</AGE>
- <ADDRESSES>
- <ADDRESS>
<ID>1</ID>
<STREET>cranbrook ave</STREET>
<POSTCODE>1231231</POSTCODE>
<CITY>NOTTINGHAM</CITY>
<COUNTRY>UK</COUNTRY>
</ADDRESS>
</ADDRESSES>
when user changes CITY to LONDON, the DataSet is updated. But I could not use DataSet.WriteXml(...) or XmlDataDocument.Save(..) to update original file as this will overwrite the whole xml file. i.e : the <MEMBER>,<GENDER>,<AGE> and their child elements will be deleted, replaced by only <ADDRESSES> elements from dataset.
So how could I update this to the original file (so only <ADDRESSES> element is affected, and <MEMBER>, <GENDER> and <AGE> stay the same?)
Many thanks for advice and suggestions,
Shar
-- modified at 13:44 Thursday 1st June, 2006
|
|
|
|
|
sepsep06 wrote: (binded to dataset that contains <addresses>)
that is the problem. The DataSet should load the entire file not just a part of it. XML DOM and/or serialization can only write the whole file. Updating discrete fields of data is what a Database is for not an XML file.
|
|
|
|
|
Hello,
Thanks again for your reply . For some reason I could not use database and all I have is an XML file. However, I have managed to solve this problem by forcing it to delete the <ADDRESSES> original children element first; and then use XpathNavigator to append children (from new updated dataset)to <ADDRESSES>. I dont think this is a very good way but it is the only working way I can think of.
Many thanks and regards,
Shar
-- modified at 20:34 Thursday 1st June, 2006
|
|
|
|
|
Hi
When I pass & to the function putnodeValue() under the IXMLDom, its converting it to &. The same thing happens for &gr; also, when &gr; is passed the value set is &gr.
How to avoid this, I want the exact value to be set which I am passing.
Pls help
|
|
|
|
|
http://www.w3.org/TR/2004/REC-xml-20040204/#charsets[^]
The following quoted from that page:
The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form, except when used as markup delimiters, or within a comment, a processing instruction, or a CDATA section. If they are needed elsewhere, they MUST be escaped using either numeric character references or the strings "&" and "<" respectively. The right angle bracket (>) MAY be represented using the string ">", and MUST, for compatibility, be escaped using either ">" or a character reference when it appears in the string "]]>" in content, when that string is not marking the end of a CDATA section.
-- modified at 23:46 Friday 26th May, 2006
|
|
|
|
|
Actually my problem is I am reading a CSV file and conveting it into XML, when one of the comma seperated value is &. I read it and set the value to the XML using IXMLDomNode's put_nodeValue() function in VC++. But the resulting output is &amp;.
Similarly when I pass > its converted to &gt;
How to over come this problem, the put_nodeValue() function is converting & to &
Is there any escape sequence to be added so that & is read as &
Thanks in Advance
|
|
|
|
|
If your source data contains an "&", it will be converted to "&" and placed into your XML document. When you parse your XML document, the "&" will be converted back to a "&".
However, you must use CDATA to store "&" as is:
using System;
using System.Collections.Generic;
using System.Text;
using System.Xml;
namespace AmpXml
{
class Program
{
static void Main(string[] args)
{
XmlDocument doc = new XmlDocument();
XmlNode node = doc.CreateNode(
XmlNodeType.Element, "amps", string.Empty);
doc.AppendChild(node);
node = doc.CreateNode(
XmlNodeType.Element, "amp", string.Empty);
doc.DocumentElement.AppendChild(node);
XmlCDataSection cdata = doc.CreateCDataSection(
"&&>>&&<<&&");
node.AppendChild(cdata);
Console.WriteLine(doc.OuterXml);
}
}
}
-- modified at 13:00 Saturday 27th May, 2006
|
|
|
|
|
I have downloaded a XML_PARSER code from this site but whenever a & is found its automatically converting it into & even if > its converting to &gt;
How to avoid this
Pls help me
|
|
|
|
|
|
Hi to All
I don't know how to use AJAX in ASP. So please if any one knows plz. help me.
If u have some ex. then plz. send me on jesalrana77@gmail.com
OK
|
|
|
|
|
Hello,
Has anyone ever seen/created such an animal?
I'm looking for a sample of a code generator that will generate code (preferably one that uses C# and the XMLTextWriter) to create an XML document structure based on an XML file as input.
I have to build some classes that allow me to generate some very complex/large/nasty XML documents for use in B2B exchange of data (like invoices, orders, etc.). A third party has dictated the structure and provided example XML documents. Instead of hand coding these classes, I'd like to be able to automatically generate them by using these example XML documents as input. This seems like a fairly easy task but I haven't sun across a demonstration of this yet.
An Example XML file (contents):
===============================
<myRootNode>
<myChildNode1>
<myChildNode2 myAttribute1="test"/>
. . .
</myChildNode1>
. . .
</myRootNode>
Example output from the code generator that takes the path of the xml file above (this is merely a simple example):
==================================================
// instantiate XmlTextWriter over file stream using UTF-8
XmlTextWriter tw = new XmlTextWriter(fileName, Encoding.UTF8);
// specify serialization details
tw.Formatting = Formatting.Indented;
tw.Indentation = 8;
tw.QuoteChar = '\"';
// No need for a start element
//tw.WriteStartDocument();
tw.WriteStartElement("myRootNode");
tw.WriteStartElement("myChildNode1");
tw.WriteStartElement("myChildNode2");
tw.WriteAttributeString("", "myAttribute1", "", "test");
tw.WriteEndElement(); // myChildNode2
tw.WriteEndElement(); // myChildNode1
tw.WriteEndElement(); // myRootNode
// No need for a start element
//tw.WriteEndDocument();
// close the stream
tw.Close();
Thanks for your time and input,
Josh Blair
Evergreen, CO
-- modified at 13:00 Thursday 25th May, 2006
|
|
|
|
|
why not use XSLT?
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forum
led mike
|
|
|
|
|
led mike,
Can you explain how I would use XSLT to generate these XML documents from empty example ones? Do you mean to transform the empty document into one that is populated with the data values?
More background: the data that I will use to populate the values in these XML documents will be coming from an ERP system (ODBC).
Thanks for the recommendation and clarification.
Josh Blair
Evergreen, CO
|
|
|
|
|
Sorry I misunderstood the first post. It sounds like you have 2 issues.
1) Generate XML data from ODBC data source.
2) Not have hard-coded XML format (element and attribute names)
First, there must be a fairly wide variety of options to accomplish those goals. I certainly do not know all of them, here are a few I am aware of.
Before I start in on a software development solution, you might look into Biz Talk Server. I have never used Biz Talk myself (only read about it) but it is highly possible it would provide a completely configuration based solution.
There may be other products as well however if for whatever reason you need to develop a solution here are some ideas.
I believe #1 is simple because I think there is a Microsoft ODBC driver that is compatible with ADO.NET. Look on MSDN for that. Obviously it is not the fastest driver.
So if we assume you can use ADO.NET to access the data then you can use the XmlSerializer to generate the XML. The bare bones generation will use the table and column names from the data source to generate the XML. Assuming that works for you then you are done and nothing is hard-coded.
If those names do not meet your requirements then you have many choices you can use to change the element and attribute names. There are Attribute (Declarative) mechanisms you can use to effect the Serialization names that are created. Again you can read about this on MSDN.
In another potential solution you could use the raw XmlSerializer XML and process those results into the desired XML using XSLT. Then the XSLT becomes in effect your "template" that can be changed to modify the end result XML without any compilation required. However it would be somewhat slower than another solution, Custom Serialization.
Basic custom serialization would in effect be hard coded. If you wanted to change the output XML format it would require compiling. However you could develop a system that reads in an XML format or mapping document and uses that to generate the output XML. This is more work but would result in you being able to change the XML mapping documents to change the output XML without any compilation involved.
Hope that helps
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forum
led mike
|
|
|
|
|
led mike,
Thanks again for your information. It is very helpful.
I must not be stating the problem and desired results appropriately. I apologize. I will try to explain myself better...
Good news: I wrote the code generator that I was looking for myself. It is a simple solution that I may post if anyone is interested. I'll give you a description of what it does: It is a console app written in C# that takes a path/filename to an example XML file as a parameter and then subsequently generates the code necessary to create a duplicate xml structure in code using the XmlTextWriter. Very simple but effective. Once this generator does its thing, you can put the output into your own class files and use them as a starting point. You can add public properties and the like to these class files and then you use them to generate XML files from ODBC queries or any other datasources. Does this make any sense? I still my not be articulating this very well.
Here is an example of what you can do with these objects once you get them built (pseudo code only):
XMLInvoice invoice = new XMLInvoice();
invoice.InvoiceNumber = "INV12355"; // may come from helper method or database query or something like that...
invoice.OtherField1 = "whatever";
invoice.OtherField2 = "whatever";
. . .
// in a looping construct that may result from records obtained from a query or the like
invoice.Lines.Add(param1, param2, etc...);
invoice.Lines.Add(param1, param2, etc...);
invoice.Lines.Add(param1, param2, etc...);
. . .
invoice.CreateXML(); // this is where the XmlTextWriter is used to generate the big nasty XML message (that the code generator helped create)
. . .
invoice.Save(filename); // for archiving purposes
. . .
B2BEngine b2b = new B2Bengine(); // object that knows how to communicate via HTTP with customers, suppliers, etc.
CustomerInfo custInfo = new CustomerInfo("MyCustomer123"); some settings info about particular customer (Ip address of server, credentials, etc.)
b2b.Send(invoice, custInfo); //
Please me know if this helped to explain my situation an better. Also, this may lead you to believe that I am approaching the problem all wrong. If that is true, please let me know your thoughts...
Thanks again,
Josh Blair
Evergreen, CO
|
|
|
|
|
Josh Blair wrote: I must not be stating the problem and desired results appropriately.
Yes I still don't get it. Based on your latest post I still think your Goal is:
1) Generate XML data from ODBC data source
Is that correct?
If it is correct then yes I do believe it is possible that you are not taking advantage of the .NET Frameworks inherent power to accomplish this. The Library has very rich capacity to connect and consume Database data. Just as powerful are the XML libraries such as the XmlSerializer that I mentioned.
"What classes are you using ? You shouldn't call stuff if you have no idea what it does"
Christian Graus in the C# forum
led mike
|
|
|
|
|
led mike,
To answer #1, let me use an example: lets take an invoice...yes some of the data comes from an ODBC datasource (ERP system), but only some of the data. Other portions of the data come from other sources of data as well (config files, other data sources like SQL Server, etc.).
I've used serialization in a limited capacity for things like reading and saving application configuration settings and such.
Are you saying that I should build business objects that are serializable? As in an Invoice object that is serializable so I can instantiate the object, fill it's properties, call it's methods and thn have the ability to serialize it to produce an XML document from this business object?
Thanks again for the clarification,
Josh Blair
Evergreen, CO
|
|
|
|
|
Here is something that might help: different portions of the xml document(s) will come from different sources of data. Again taking an invoice as an example (but there are other types of docments as well):
I have to send invoices to a third party. This third party defined the xml structures that I have to populate and did not provide schemas or DTDs. A large portion of the data that I need to send to this thord party will originate from a legacy ERP system that does offer an ODBC driver. I can obtain the data from this system, no problem...already got that part licked.
The invoice XML document has a "header section" which contains sub-sections like "ship-to section", "buyer section" and so on nested within the "header section".
It also contain a "line item section" where there can be one to many line items in this section.
Some of the data that populates the "header section" will come from the invoice header in the ERP system (via ODBC). Other parts will come from a configuration file, while other data will come from database tables not originating from the ERP system (maybe a SQL Server).
Most of the data that will populate the "line item section" will come from the ERP system from the lines on the invoice.
Serialization might be the proper approach. I think the code generator that I wrote may be misusing the .NET framework because it is essentially reproducing the features of serialization. BUT...when using serialization, bdo you have full control over how things get serialized? I can't have all the "junk" that comes with serialization out of the box. When I say "junk", I mean the xml namespaces and extra crap not allowed by this third party. As in: xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance".
Also, I need to have full control over the order of how elements are ordered and nested. Is this possible with .NET serialization? I'd rather not have to transform the serialized business object before I send it off because I'm not really versed at XSLT.
Josh Blair
Evergreen, CO
|
|
|
|
|
It sounds to me like you could use a DataSet to coalesce the disparate sources. See some DataSet articles I know there are some on CodeProject. Josh Blair wrote:I need to have full control over the order of how elements are ordered and nested.
A DataSet fulfills that requirement. You can design the tables and relationships to your requirements.
Josh Blair wrote: BUT...when using serialization, bdo you have full control over how things get serialized?
Yes there are several different ways to control serialization.
Josh Blair wrote: When I say "junk", I mean the xml namespaces and extra crap not allowed by this third party. As in: xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance".
That makes no sense at all, those are XML standard namespaces.  Anyway that should be possible one way or another. I expect you can control that using declarative attributes in your code. Look at the XmlSerializer and the XmlRootAttribute attribute.
|
|
|
|
|
Josh Blair wrote: Other portions of the data come from other sources of data as well
ahhh... didn't know that.
Do these source data schemas change?
Why do you keep refering to XmlTextWriter? Do you have some requirement to use it? Why?
|
|
|
|
|
led mike,
Not sure if these XML structures (schemas) change very often. They come from a company from Japan (from a division in Italy). I think they are pretty solid/permanent. Also, I'm not sure why they didn't provide schemas or DTDs either...
I am using the XmlTextWriter only because it is fast (not that speed is really and issue at this point). I used the XMLDocument object in a previous cXML project that was very similar to this project and it seemed a little slower to generate the xml docs. I just wanted to try the XmlTextWriter to see if it was noticably faster. It is also easier to use the XmlTextWriter in my code generator. I also thought about the StringBuilder and it work just as well probably. The XmlTextWriter has a fwe handly features like being able to close off the element and stuff like that.
Josh Blair
Evergreen, CO
|
|
|
|
|
I think I understand what you're talking about, although it doesn't make much sense. You take an XML document as input and create the code that will generate that XML document. I've never seen anything like that before, but I'm pretty sure you could just write one yourself using an XmlReader and a StringBuilder (or better yet - CodeDom).
|
|
|
|
|
Yes, the output from the code generator alone doesn't offer much by itself. So then, once I have the code that produces the XML document (an empty version with no invoice data), I add to that code. I add public properties with get and set accessors. I add the ablity to add line items to a "line itme collection", things like that. So from my code, I can grab all the data necessary that will eventually populate this document, then I instantiate this xml invoice business object filling its properties, collections, etc. Then i call a "create" method which generates a new xml document with the proper structure containing all the invoice data from my ERP system and other data sources. Am I approaching this bass-ackwards?
Thanks,
Josh Blair
Evergreen, CO
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
