Activity for VTD-XML: The Future of XML Processing
-
jimmy zhang posted a comment on discussion Open Discussion
yes, why?
-
Ioan Stan modified a comment on discussion Open Discussion
I'm also interested in the status of this project. Would be great also if it was migrated to github or someplace with more visibility / chances of contributions. I think collaboration is difficult on sourceforge. WDYT @jzhang2004 ?
-
I'm also interested in the status of this project. Would be great also if it was migrated to github or someplace with more visibility / chances of contributions. I think collaboration is difficult on sourceforge.
-
Martin Lichtin posted a comment on discussion Open Discussion
Hi Jimmy, will you create a new release at some point?
-
Mirko Budszuhn created ticket #16
XPath empty-node-set comparison bug
-
XPath white-space error
-
Robert Yeager posted a comment on discussion Open Discussion
Hi, I am using the VTD-XML Java library v2.13.4 and have a test case that is causing a null pointer exception within the library. Should I report the bug with the test case? Is anyone maintaining the project? I don't see any activity in over a year.
-
Rainette posted a comment on ticket #4
Hi Narasimha, yes i did this bad thing to copy/paste the code and removed the static attribute. I used Maven and i didn't want to rewrite and repackage the libraray so i put my fixed class in the a package named exactly as it is in the library. So the classloader use it insteaf of the original one. That's did the job... PS : sorry for my english :-(
-
NARASIMHA modified a comment on ticket #4
May I know when is going to have next release?
-
Hi Rainette, Did you rewrite the AutoPilot class without static members?
-
Hi jimmy, for now is there any solution to it ?
-
Hi Rainette, Could you please explain how did you rewrite your code to remove this this static members. Thanks in advance.
-
I'm also facing the same issue when I'm doing the load test with mutiple threads. The same request is failing if I increase the threads and ppoin of error is at Autopilot class. I haven't fixed yet.
-
Andrei Pashkin modified a comment on discussion Open Discussion
Hello, in my project I deal with deeply nested XML documents and sometimes I get Depth exceeds MAX_DEPTH errors. It seems that MAX_DEPTH is a hardcoded constant - would it make sense to make it configurable to facilitate parsing of deeply nested XML?
-
this is a bug that is /will be fixed...you can fix it yourself... it was a wrong decision to make it static
-
It will be fixed in the next release!!
-
Java AutoPilot default namespace searches return additional incorrect nodes
-
are you using vtd-xml standard or extended vtd-xml?
-
Can you be more specific on what went wrong or unexpected?
-
Hello, in my project I deal with deeply nested XML documents and sometimes I get Depth exceeds MAX_DEPTH errors. It seems that MAX_DEPTH is a hardcoded constant - would it make sense to make it configurable to facilitate parsing of deeply nested XML? If yes - I would like to submit a patch.
-
Attaching a revised test case that just makes the code more correct, to remove the t++ increment within the loop for the TextIter approach: while ((t = ti.getNext()) != -1) { nodeText += vn.toString(t++); } while ((t = ti.getNext()) != -1) { nodeText += vn.toString(t); }
-
Hi Jimmy, I have put together a comprehensive test, attached, that demonstrates various ways in which the VTD-XML parser methods provide varying results when the goal is to fetch all the text of a node. The test case consists of a standard single text < 1MB of data, a large CDATA value > 2MB, and a mixed content test. For each input XML, the code tests 4 ways of fetching the node text: xpath text() VTDNav getXPathStringVal() VTDNav getTokenType() loop TextIter Here is the output from the attached...
-
Sorry I may have misunderstood your question... to access mixed content huge CDATA text... you may want to resort to XPath or an otherwise little-known class called TextIter() it is part of the VTD-XML api... This class iterates through all text nodes of an element. VTDNav has getText() which is inadequate for mixed content style of XML. text nodes include character_data and CDATA. Since version 2.8, selectText(), selectComment(), and selectPI() were added ... you can basically instantiate the class......
-
Hi Jimmy, I tried getXPathStringVal() as follows: VTDNav vn = vg.getNav(); if (vn.matchElement("root")) { System.out.println("getXPathStringVal() val = "+vn.getXPathStringVal()); } Here is the test XML: <root>Some mixed<child>child text</child>content text</root> Here is the output: getXPathStringVal() val = Some mixedchild textcontent text I don't understand why it also grabbed the child node's text. I was expecting it would emit "Some mixedcontent text" Attached is the new test case. I also tried...
-
you won't need to worry about this in XPath since 2.13... there is a new method that handles mixed content XPath according to the spex you could use a new method called getXPathStringVal(). Could you take a look and let me know what you think?
-
you could use a new method called getXPathStringVal(). Could you take a look and let me know what you think?
-
problem parsing xml document with unicode characters past U10000
-
this bug is marked as fixed
-
Issue when parsing CDATA
-
Single Quote is throwing error
-
I am closing this issue... let me know if you need more assistance
-
Hi Jimmy, Thanks, that makes sense, but what about when an XML node has mixed content like this: <root>Some mixed<child>child text</child> content text</root> The VTDNav.getText() doesn't handle mixed content (VTDNav.getText() just returns "Some mixed" for the XML above instead of "Some mixed content text"), which is why I attempted to handle with my while() loop. So am I hitting a situation where a routine that might work for mixed content then breaks when it hits large CDATA > 1MB? Can you please...
-
ok.. this is actually not a bug... vtd will break CDATA or char data longer than 1MB into multiple tokens of maximum 1MB each... and when you call toString()... VTD will automatically assemble those tokens back into the one of desired length.. the problem now is that you are calling toString on the first token (which already assembles teh entire string for you), then you move on to the next token and merge with the string representation of the second token (which could include the third or fourth...
-
Unexpected result reading node text from a Base64 CDATA value
-
Thanks! will look into it and get back
-
Unexpected result reading node text from a Base64 CDATA value
-
Chew posted a comment on discussion Open Discussion
Hey Jimmy, I'm so sorry I didn't answer, I didn't get any notifications on updates on this topic although I explicitly activated notifications. Thank you so much! This helps a lot with our project organization. Thanks a ton!
-
John L posted a comment on discussion Help
I have been playing with this, however when I move to latest version from 2.11 it does not work I was using this example http://javawitharun.blogspot.co.uk/2014/03/vtd-xml-parser.html
-
It is now on maven central. fyi
-
Do you know how to do it? I will try my best but I need to investigate.
-
Hi Jimmy, I need a newer version of VTD-XML due to the unicode fixes. I work with Maven and need it as a public Maven dependency. Is there any chance that newer versions of VTD-XML will be uploaded to Maven Central in the near future? Thanks, Erik
-
download 2.13_4 and you will find the fix
-
VTD-XML: The Future of XML Processing released /vtd-xml/ximpleware_2.13_4/ximpleware-2.13-4-java.zip
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
