|
From: Erik F. <eri...@un...> - 2015-05-11 07:17:29
|
Hi again, so I used vn.getNestingLevel() to determine the maximum depth of an element in my XML document. The output is 33, so the depth is 32, just two more than the constant of VTDGenHuge allows us. HOWEVER I don’t know whether I don’t also have other documents with a deeper depth. Since the parser opts out already at the document with a depth of 32, I can’t say if even deeper documents would follow. What can I do about it? Thanks very much, Erik > On 09 May 2015, at 10:09, Erik Fäßler <eri...@un...> wrote: > > Hmm, I wouldn't know, this was not exactly something I kept track of until now. Didn't I append the file to the question, perhaps you know a very quick way to determine the depth? Otherwise I will write some script to count the depth. But I can do this only as early as Monday as I currently don't have this particular file with me. > > Best, > > Erik > > > > On 08 May 2015, at 22:39, jz...@xi... <mailto:jz...@xi...> wrote: > >> How deep is your xml document processed in vtd-xml huge? >> >> >> >> ----- Original Message ----- >> From: >> Erik Fäßler <eri...@un... <mailto:eri...@un...>> >> >> To: >> <vtd...@li... <mailto:vtd...@li...>> >> Cc: >> >> Sent: >> Wed, 6 May 2015 16:29:33 +0200 >> Subject: >> [Vtd-xml-users] VTD Huge: Depth exceeds MAX_DEPTH >> >> >> Hi there, >> >> I was trying to parse the XML file in the attachment with the VTD Huge parser. I need the Huge parser because originally, the XML contents of the file are just part of a file as large as 1.3GB. >> Parsing this file fails with the error >> >> com.ximpleware.extended.ParseExceptionHuge: <http://com.ximpleware.extended.parseexceptionhuge/> Other Error: Depth exceeds MAX_DEPTH >> Line Number: 4856 Offset: 70 >> >> Using VTD XML 2.11. >> With the normal VTD it is working because there, the MAX_DEPTH constant is set to 254 instead of only 30 on VTD Huge. Would it be possible to make this configurable (e.g. by a Java system property like java -Dcom.ximpleware.max_depth) <http:/> or is there any reason why this constant should absolutely stay at 30? It would make VTD fail for my use case which would be too bad since my primary XML tooling is developed around VTD XML. >> >> Thanks and best regards, >> >> Erik >> > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________ > Vtd-xml-users mailing list > Vtd...@li... > https://lists.sourceforge.net/lists/listinfo/vtd-xml-users |