|
Appreciate the feedback. As in many projects, some things are being decided by other people. I'm just trying to get a handle on what to expect. If it has to be done this way, it has to be done this way  .
Past projects have exchanged data between devices using binary. This has disadvantages - byte swapping issues, messages tied to data structures, etc.
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I am receiving xml from an external web service that I am consuming in a C# application.
The xsd has this line:
<xs:element type="xs:byte" name="contract_term"/>
Most of the files received have this element set to a value but I have just come across one that has it empty:
<contract_term/>
Is this valid, or should I raise it with the web service producer?
|
|
|
|
|
It's syntactically valid XML; what's the problem?
Use the best guess
|
|
|
|
|
I would expect that a value of 0 to 255 would be present for an element marked as byte and it should never be empty. It caused the .NET XmlSerializer to throw an exception when deserializing the data.
I have done a work around by deserializing to a string instead and having an additional property that returns the result parameter of byte.TryParse on the string, but it's a bit messy.
|
|
|
|
|
If you think it's wrong then you should talk to the provider of the XML data.
Use the best guess
|
|
|
|
|
I have raised it with them, but not being very knowledgeable in the finer points of XML/XSD I wasn't sure about it's validity.
|
|
|
|
|
Try making the byte a nullable. As far as I know byte is generally a value type which means it can't be null.
e.g. in c#
byte? elementName
|
|
|
|
|
Yes, you are correct about byte being a value type (in .NET anyway). I haven't tried using nullable so don't know how the XmlSerializer will respond to it - could be interesting!
|
|
|
|
|
I have had a look round a few sites but could not find a definitive statement on this.
Use the best guess
|
|
|
|
|
The dev at the company who provide the web service got back to me saying there should always be a value, and they would of course fix it.
|
|
|
|
|
It is valid -- but, the creator of the XSD did not indicate that it was required -- and you have assumed that it is required. If your code cannot tolerate that -- then modify the XSD to make it required and have whoever produces the XML give it a default value....
However, this is simply pushing it off to the side. This is an issue that does not relate to XML per se -- it relates to best practices about defining and validating data.
The XSD defines the structure and rules of XML -- so the designer of the schema must describe the data perfectly and consumers must not make assumptions that are not supported by the XSD.
|
|
|
|
|
I have a XML which has list items like
<list type="expl" margin="0">
<li label="(1)">
<p num="n">
<text>
(1) A person
is guilty of an offence if:
</text>
</p>
</li>
</list>
<list type="expl" margin="0">
<li label="(a)">
<p num="n">
<text>
(a) the
person deals with money or other property; and
</text>
</p>
</li>
</list>
The output i need is like
<list type="expl">
<li label="(1)">
<p num="n">
<text>A person is guilty of an offence if:</text>
</p>
<list type="expl">
<li label="(a)">
<p num="n">
<text>the person deals with money or other property; and</text>
</p>
</li>
</list>
</list>
Effectively if List appears as consecutive siblings, and they are of different types (eg, (1)/(a)/(i)) they must be nested inside the previous list item.
|
|
|
|
|
<Messages>
<category Name="Main">
<message id="1" title="one" name="Name1" Description="Description1">
</message>
</category>
<category Name="Main1">
<message id="2" title="two" name="Name2" Description="Description2">
</message>
</category>
|
|
|
|
|
|
public static string filePath = HttpContext.Current.Server.MapPath("~/App_Data/Messages.xml");
public static XmlDocument xmlDoc = new XmlDocument();
XmlNode _xmlNode = xmlDoc.CreateElement("category");
XmlAttribute _xmlCategoryName = xmlDoc.CreateAttribute("Name");
_xmlCategoryName.Value = categoryName;
_xmlNode.Attributes.Append(_xmlCategoryName);
// Add Message Node
XmlElement _xmlElement = xmlDoc.CreateElement("message");
XmlAttribute _xmlId = xmlDoc.CreateAttribute("id");
_xmlId.Value = Convert.ToString(ID);
_xmlElement.Attributes.Append(_xmlId);
XmlAttribute _xmltitle = xmlDoc.CreateAttribute("title");
_xmltitle.Value = Convert.ToString(title);
_xmlElement.Attributes.Append(_xmltitle);
XmlAttribute _xmlname = xmlDoc.CreateAttribute("name");
_xmlname.Value = Convert.ToString(name);
_xmlElement.Attributes.Append(_xmlname);
XmlAttribute _xmlDescription = xmlDoc.CreateAttribute("Description");
_xmlDescription.Value = Convert.ToString(description);
_xmlElement.Attributes.Append(_xmlDescription);
_xmlNode.AppendChild(_xmlElement);
xmlDoc.DocumentElement.AppendChild(_xmlNode);
|
|
|
|
|
This is not the document you want for figuring out CRUD. You need the XSD to do that properly. You could guess and as long as the database column names matched you *might* be able to guess correctly, but...I would not be helping you if I recommended that you do that.
If you can write your own query to select a row and if you also had access to ADO.NET -- you could have the table tell you its schema and then the query could be written properly.
This method that you are using -- is not a great idea -- you can have some success in doing it, but not for long and it is very likely that you will manage to put a row in the database that will be junk data because you do not know the schema -- you are just making blind CRUD operations.
A better choice might be stored procedures because you can just provide the parameters from the client side. At any rate, the less you count on being smart on the client side, the better off you will be.
|
|
|
|
|
good morning to everyone,
i want to display some of the questions stored in an xml file on a listbox in wpf,only one questions should be displyed on listbox by using a button,it shows different questions each time whenever i press next button,please send me code for this
thanks in advance
|
|
|
|
|
adinarayana09580 wrote: please send me code for this
See point 2[^].
Use the best guess
|
|
|
|
|
Before you read on, this is not about checking for valid XML syntax or schema.
I would like to be able to check if the user is opening an XML file that has data for my application only. If they try to open any other XML file the application should warn them.
The XML file data is serialized via XmlSerializer.
Thanks,
Mark
|
|
|
|
|
Add some kind of identifier for your application, perhaps also including a version number.
|
|
|
|
|
Does such a thing require adding a new namespace?
Mark
|
|
|
|
|
OK, I'd be first to post a link to Parsing Html The Cthulhu Way
[^] if anyone suggests Regular Expressions, but I have a problem using an XmlDocument (and therefore XPath) with an HTML file I'm downloading.
The page is a list of files to download -- I need to extract the hrefs from the as, obviously I'd prefer to use XPath to do that.
0) The file doesn't contain an opening <HTML> tag (it does have a closing </HTML> tag  ) -- I can tack one on, that's not a big deal.
1) It contains at least one entity (and possibly other entities) and the XmlDocument doesn't like that. 
So I need options, people!
I can summon Cthulhu. 
I can use Regular Expressions to replace any offending entities and then feed the result to an XmlDocument.
What other options might there be?
|
|
|
|
|
HTML != XML
Use the HTML Agility Pack[^] instead.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Ah, sooooo... let the summoning begin!
Oh, mighty Cthulhu! Wise and terrible! I ask your assistance as my days have been blighted with some gnarly HTML! Please, oh lord, come smite the bare buttocks of the wretch who hast wrought this travesty. I will repay you with a pint of bitter. Not a measly USian pint mind you, but a proper Britsh pint.
|
|
|
|
|
No need to make that call to R'lyeh yet; the HAP makes parsing an HTML document simple:
HtmlDocument doc = new HtmlDocument();
doc.Load(@"path\to\your\file.htm");
foreach(HtmlNode link in doc.DocumentElement.SelectNodes("//a[@href"])
{
string url = link["href"].Value;
Fhtagn(url);
}
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
