|
Have you tried using a profiler? A colleague of mine wrote an xml parser/validator in .Net for large files and the first file would complete in about 20-30 minutes. After the first though, it would get incredibly slow, taking around 18-30 hours to process 50mb files. When we checked the memory allocations there were about 10 times more than necessary. The app was running out of memory and continually hitting the page file on disk to make up the difference. All of that because he didn't understand the immutable nature of .Net Strings.
EDIT - I realize you are not using .Net, but I am thinking you could try a profiler for java.
That is the best advice I can give, good luck friend. 
|
|
|
|
|
I feel for this poster....
The issue is most likely poor XML and XSLT design. Too many people refuse to take the time to understand their data and XML and in the rush to 'get something working' they create a schema that is bloated, incomplete and that requires a lot of resources to even attempt to use.
Six days for 100MB? Yes - I can say that the schema does not represent the data well and the XSL is probably even worse because it must translate this rickety XML into something that might be even more poorly designed and implemented and it is apparent that the XSL has been where all of the changes and fixes have been applied.
For starters -- do not avoid using attributes simply because elements seem 'easier' -- they are not. Things that describe a thing -- are attributes. Things that own things -- are usually elements.
I post here because -- when you try to engineer a system and write the entire application at the same time -- all the while saying -- just get it running, we'll fill in the details later -- and also you take alot of shortcuts ('it will be easier if we do ....')....all you are doing is moving the work further down the line and making it more difficult....
There is a definite amount of work that must be done -- never assume that you can avoid it and do as much up front as you can.
|
|
|
|
|
I have a program I have written that displays the contents of a xml file in a browser. I am trying to make it more user friendly for people to change the xml files without opening them in notepad or a canned xml editor. What I would like to do is be able to pull the information from the xml file into a webpage and allow the users to make changes and save it back to the xml file. I've done google searches for about a week and can't come up with a good way to do it. Any suggestions would be much appreciated.
|
|
|
|
|
I'm doing one currently where the xml is shown in the browser control (after xslt applied to it) and if the user needs to add data (we are not changing anything)I have a form come up to fill in the data. This was the most direct method for me but if that doesn't work you may have to look in the javascript direction.
|
|
|
|
|
Marc Clifton has a good article here where he parses the schema, and produces a dialog based form showing the message content. Well worth a look.
Ger
|
|
|
|
|
Is there any free xml tool to acquire xpath value of some element or attribute?
thanks!
|
|
|
|
|
Hello. Im trying to create an xml schema that can capture the following behavior:
1. <info> element should be the first inside <root>
2. <ParamA>, <ParamB>, <ParamC>, <ParamD>, and <ParamE> are optional, should appear after the <info> element and can appear in any order.
The following xml are valid:
<root>
<info></info>
<ParamA></ParamA>
<ParamB></ParamB>
<ParamC></ParamC>
<ParamD></ParamD>
<ParamE></ParamE>
</root>
OR
<root>
<info></info>
<ParamB></ParamB>
<ParamD></ParamD>
<ParamC></ParamC>
<ParamA></ParamA>
<ParamE></ParamE>
</root>
The following xml is NOT valid:
<root>
<ParamB></ParamB>
<ParamD></ParamD>
<ParamC></ParamC>
<ParamA></ParamA>
<info></info>
<ParamE></ParamE>
</root>
I have tried doing:
<xs:sequence>
<xs:element name="info" minOccurrence="0">
<xs:all>
<xs:element name="ParamA" minOccurrence="0">
<xs:element name="ParamB" minOccurrence="0">
<xs:element name="ParamC" minOccurrence="0">
<xs:element name="ParamD" minOccurrence="0">
<xs:element name="ParamE" minOccurrence="0">
</xs:all>
</xs:sequence>
This causes an invalid xml schema error because an all model group is not allowed to appear inside another model group.
I've also tried substitution:
<xs:complexType name="information">
<xs:all>
<xs:element name="info" minOccurrence="0">
</xs:all>
</xs:complexType>
<xs:complexType>
<xs:complexContent>
<xs:extension base="information">
<xs:all>
<xs:element name="ParamA" minOccurrence="0">
<xs:element name="ParamB" minOccurrence="0">
<xs:element name="ParamC" minOccurrence="0">
<xs:element name="ParamD" minOccurrence="0">
<xs:element name="ParamE" minOccurrence="0">
</xs:all>
</xs:extension>
</xs:complexContent>
</xs:complexType>
This is still getting an xml schema error on the usage of all model group.
Does anyone have a similar problem or have any idea how to create an xml schema for the desired behavior stated above? Thanks.
modified 27-Apr-12 5:56am.
|
|
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="root">
<xs:complexType>
<xs:sequence>
<xs:element name="info" maxOccurs="unbounded" minOccurs="1">
<xs:complexType>
<xs:all>
<xs:element ref="paramA" maxOccurs="1" minOccurs="1"/>
<xs:element ref="paramB" maxOccurs="1" minOccurs="1"/>
<xs:element ref="paramC" maxOccurs="1" minOccurs="1"/>
<xs:element ref="paramD" maxOccurs="1" minOccurs="1"/>
<xs:element ref="paramE" maxOccurs="1" minOccurs="1"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="paramA" type="xs:string"/>
<xs:element name="paramB" type="xs:string"/>
<xs:element name="paramC" type="xs:string"/>
<xs:element name="paramD" type="xs:string"/>
<xs:element name="paramE" type="xs:string"/>
</xs:schema>
|
|
|
|
|
Hello,
Below is my XML document.
<GetCountersResult>
<GetCountsResult xmlns="">
<Count>
<ID>FP108MR</ID>
<Value>0</Value>
<Part>Z9999</Part>
</Count>
</GetCountsResult>
</GetCountersResult>
I need to remove only <GetCountsResult> node so that my xml document remains as below.
<GetCountersResult>
<Count>
<ID>FP108MR</ID>
<Value>0</Value>
<Part>Z9999</Part>
</Count>
</GetCountersResult>
I used the following code to convert Dataset to a XMLdocument.
Dim dtCounter As New DataSet("GetCountsResult")
oDatabase.Connect()
oDatabase.PopulateDataSet("Count", "Get_Current_Counter", True, dtCounter)
Dim sw As New StringWriter
dtCounter.WriteXml(sw, XmlWriteMode.IgnoreSchema)
Dim xmldoc As New XmlDocument
xmldoc.LoadXml(sw.ToString())
Please help me in getting this.
Thanks.
|
|
|
|
|
The ReplaceChild method of XmlNodeclass explained here http://msdn.microsoft.com/en-us/library/system.xml.xmlnode.replacechild.aspx[^] can be used for replacing the desired nodes as shown below:
void Main()
{
string xmlCounters =
@"<GetCountersResult>
<GetCountsResult xmlns="""">
<Count>
<ID>FP108MR</ID>
<Value>0</Value>
<Part>Z9999</Part>
</Count>
</GetCountsResult>
<GetCountsResult xmlns="""">
<Count>
<ID>FP108MR No2</ID>
<Value>0 No2</Value>
<Part>Z9999 No2</Part>
</Count>
</GetCountsResult>
</GetCountersResult>";
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.LoadXml(xmlCounters);
var countNodes = xmlDoc.GetElementsByTagName("Count");
for (int i=0; i < countNodes.Count; i++)
{
xmlDoc.DocumentElement.ReplaceChild(countNodes[i], countNodes[i].ParentNode);
}
string fileName = @"F:\ModifiedXml.xml";
xmlDoc.Save(fileName);
}
modified 25-Apr-12 4:34am.
|
|
|
|
|
Thank you so much. I will try this.
|
|
|
|
|
You're welcome. After trying please give your feedback and if it is helpful you may consider to vote.
Thank you for the response.
|
|
|
|
|
I have an integer attribute declared in the xsd file. In the xml file, I need to use hex for the value. I can’t find info about the syntax about hex value.
I tried something but neither
<MyData MyValue="0x52590"/> nor <MyData MyValue="#52590"/> works. Any clues are appreciated.
modified 10-Apr-12 9:38am.
|
|
|
|
|
<MyData MyValue="0x52590"/>
Independent ACN Business OwnerMake toll free long distance calls from your smart phone with ACN Mobile World. When connected via wifi, calls will not use any of your minutes or data, nor will there be any roaming charges.
Certain conditions apply. See my website for details.
Within you lies the power for good - Use it!
|
|
|
|
|
Frank W. Wu wrote: I have an integer attribute declared in the xsd file. In the xml file, I need to use hex for the value. I can’t find info about the syntax about hex value.
Because that isn't possible.
Definition of an 'int' is a optional sign followed by decimal digits. Nothing else.
The definition.
http://www.w3.org/TR/xmlschema-2/#int[^]
In terms of a solution - convert the hex value to an integer or change the xsd.
|
|
|
|
|
In this[^] article, the author uses two notations to access elements in an XML DOM object
Element elem1 = root[L"aa|bb|cc"] and
Element elem1 = root[L"aa"][L"bb"][L"cc"] Is there a name for these two different notations, and if so what are they?
Independent ACN Business OwnerMake toll free long distance calls from your smart phone with ACN Mobile World. When connected via wifi, calls will not use any of your minutes or data, nor will there be any roaming charges.
Certain conditions apply. See my website for details.
Within you lies the power for good - Use it!
|
|
|
|
|
I'm having next xml file and I want to make an xsl template to select the name of node that containts some values for child nodes.
xml:
<pre lang="HTML">
<nodes>
<n1>
<name>AA</name>
<fields>
<field1>a</field>
<field2>b</field>
<field3>c</field>
</fields>
</n1>
<n2>
<name>BB</name>
<fields>
<field1>a</field>
<field2>x</field>
<field3>c</field>
</fields>
</n2>
<n3>
<name>BB</name>
<fields>
<field2>x</field>
<field3>c</field>
</fields>
</n3>
</nodes>
I want to get only the nodes that have at fields a and not b (a and !b), so every fields node can have a variable number of childs. In this example it will be valid only n2
|
|
|
|
|
The XML you posted is mal-formed, but after cleaning it up a little I found that
"*/*[fields/*='a' and not(fields/*='b')]"
seems to work.
|
|
|
|
|
I'm trying to iterate the namespace declarations in an XML document so I can add them to the XmlNamespaceManager, but it's not working.
Given an XML document like:
<foo:bar xmlns:foo='the URI for foo' />
I expect:
System.Xml.XmlDocument doc = new System.Xml.XmlDocument() ;
doc.Load ( args [ 0 ] ) ;
System.Xml.XmlNamespaceManager mgr = new System.Xml.XmlNamespaceManager ( doc.NameTable ) ;
foreach ( System.Xml.XmlNode nod in doc.SelectNodes ( "//*[@xmlns:*]" , mgr ) )
...
to select that element, but it doesn't.
Am I missing something? Does SelectNodes just not want to select by namespace attributes?
Edit: I now see that this is the defined behaviour of XPath 1.0; I don't like it, but there it is.
modified 29-Mar-12 18:00pm.
|
|
|
|
|
Kinda sounds like you're putting the cart before the horse. You're trying to walk the document to select the namespaces, but in order to walk the tree with xpaths, you really need the namespaces first. Do you not know the structure of your XML? You're really supposed to know your namespaces first, and just use them.
You can, I think, walk the tree through the object model and pull out the namespace prefixes and URIs--using some combination of the NamespaceURI property, and the GetNamespaceOfPrefix and/or GetPrefixOfNamespace methods. There's probably a much more efficient way, though--maybe the XMLReader? Quick search .. try this:
http://www.hanselman.com/blog/GetNamespacesFromAnXMLDocumentWithXPathDocumentAndLINQToXML.aspx[^]
|
|
|
|
|
woopsydoozy wrote: Do you not know the structure of your XML?
Correct.
woopsydoozy wrote: in order to walk the tree with xpaths, you really need the namespaces
I know the one for xmlns, and it's in the manager, but I can't use it.
I'll read the suggested page. Thanks.
|
|
|
|
|
Having read the suggested page and tried a few more things I now understand a lot more about the problems I'm having, but it still doesn't explain why I can't use SelectNodes to get the information I need.
|
|
|
|
|
Is your issue maybe in using the namespace in the xpath? In your original XML snippet, for example, if you wanted the "box" element in the foo namespace, you'd select foo:box. You do have to add the "foo" namespace to your manager to use it, though:
mgr.AddNamespace("foo","the URI for foo") Just declaring a namespacemanager does not automatically load all the namespaces.
When it's a default namespace (no prefix), the trick I've used in the past is to add a new namespace that has the same URI:
mgr.AddNamespace("foo2","the URI for foo") This allows me to query for foo2:box.
Or maybe you're just wondering why you can't query using xmlns as an attribute? I don't know the technical answer except that it's special somehow, not available as a standard attribute. You can still access it in xpath/xslt if you need to--check out the namespace-uri method, for example.
|
|
|
|
|
woopsydoozy wrote: Is your issue maybe in using the namespace in the xpath?
No, I got that now.
woopsydoozy wrote: Just declaring a namespacemanager does not automatically load all the namespaces
Right, and now I understand why. I hope to write at least a Tip on it soon.
woopsydoozy wrote: When it's a default namespace ...
Right, even though it seems bogus (I still need to investigate further).
Edit: The W3C spec for XPath 1.0 (section 2.3 Node tests) says in part:<br />
"<br />
A QName in the node test is expanded into an expanded-name using the namespace declarations from the expression context. This is the same way expansion is done for element type names in start and end-tags except that the default namespace declared with xmlns is not used: if the QName does not have a prefix, then the namespace URI is null (this is the same way attribute names are expanded). <br />
"<br />
<a href="http://www.w3.org/TR/xpath/#node-tests">http:
<br />
So it's W3C's fault and I still don't see why they would define it that way. :mad:<br />
woopsydoozy wrote: maybe you're just wondering why you can't query using xmlns as an attribute
Yes, and also as the namespace of an attribute.
<br />
Edit: The W3C spec for XPath 1.0 (section 5.3 Attribute Nodes) says in part:<br />
"<br />
There are no attribute nodes corresponding to attributes that declare namespaces <br />
"<br />
modified 29-Mar-12 17:22pm.
|
|
|
|
|
Michael Kay rocks (check out his books, if you're doing anything with XSLT): http://www.stylusstudio.com/xsllist/200403/post30310.html
And attributes don't inherit the namespaces of their containing element by default. They only have namespaces if they have their own namespace prefix (which I don't think I've ever seen in practice). So if you had this XML:
<demo xmlns:foo='foo URI'><foo:box contents='zombie cat'/></demo>
and you wanted to find out what was in the box, you'd add foo and its URI to your namespace manager and get /demo/foo:box/@contents. Only with this XML:
<demo xmlns:foo='foo URI'><foo:box foo:contents='zombie cat'/></demo>
would you need to specify the attribute's namespace: /demo/foo:box/@foo:contents.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
