Menu
▾
▴
vtd-xml-users — This mailing list is for users or people interested in VTD-XML
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(6) |
Jul
(21) |
Aug
(40) |
Sep
(7) |
Oct
(41) |
Nov
(52) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(49) |
Feb
(37) |
Mar
(84) |
Apr
(11) |
May
(29) |
Jun
(9) |
Jul
(19) |
Aug
(9) |
Sep
(6) |
Oct
(5) |
Nov
(15) |
Dec
(3) |
| 2008 |
Jan
(7) |
Feb
(11) |
Mar
(25) |
Apr
(50) |
May
(7) |
Jun
(8) |
Jul
(10) |
Aug
(18) |
Sep
(1) |
Oct
(15) |
Nov
(1) |
Dec
(9) |
| 2009 |
Jan
(5) |
Feb
(2) |
Mar
(3) |
Apr
(5) |
May
(10) |
Jun
(4) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(15) |
Nov
(13) |
Dec
(6) |
| 2010 |
Jan
|
Feb
(3) |
Mar
(4) |
Apr
(6) |
May
|
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2011 |
Jan
(19) |
Feb
(39) |
Mar
(28) |
Apr
(6) |
May
(7) |
Jun
(9) |
Jul
|
Aug
(1) |
Sep
|
Oct
(8) |
Nov
(3) |
Dec
(12) |
| 2012 |
Jan
(2) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
(4) |
Jun
(3) |
Jul
(10) |
Aug
(2) |
Sep
(13) |
Oct
(24) |
Nov
(3) |
Dec
(1) |
| 2013 |
Jan
(11) |
Feb
(5) |
Mar
(4) |
Apr
(3) |
May
(3) |
Jun
(5) |
Jul
(7) |
Aug
(16) |
Sep
|
Oct
(7) |
Nov
(11) |
Dec
|
| 2014 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
(11) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(3) |
Sep
(5) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
|
Jul
(4) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <sat...@gm...> - 2022-05-05 09:47:59
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div> <div> </div> <div>I'm working for a small company and would like to use vtd-xml in a software. Since the company is developing for a customer who wants the product to be proprietary, I was looking for an alternative license than GPL.</div> <div> </div> <div>Ximpleware, however, does not reply to emails for license quotation. I've tried following pages and email addresses.</div> <div> </div> <div>http://www.ximpleware.com/ </div> <div>https://vtd-xml.sourceforge.io/faq.html</div> <div>sa...@xi...</div> <div>in...@xi...</div> <div class="signature"> </div> <div class="signature"> </div> <div class="signature">Any ideas, how to solve the contact issue and receive a commercial license? Is anyone involved with Ximpleware in this forum?</div> <div class="signature"> </div> <div class="signature">Thanks and best regards,</div> <div class="signature"> </div> <div class="signature">Sata</div></div></body></html> |
|
From: <pet...@ho...> - 2019-03-04 09:15:53
|
Hello We use the C++ version of the parser. It seems it can't handle emoticons. I saw it probably fixed in the commit dated 15-7-2017 with commentary "added supplementary character support for string comparison conversion functions." However this is only the java code. Is it possible to update the C++ code as well? Regards, Peter |
|
From: OGrandeDiEnne <ogr...@gm...> - 2019-01-17 11:00:24
|
As far as I understand, the library is licensed as GPL2. Do you also offer a commercial license to incorporate in a software product? If so, can you provide the pricing and information about the license? Thanks. |
|
From: <jz...@xi...> - 2018-11-19 22:36:51
|
Sorry for the late reply, but the maximum attribute value length is 1MB... if it exceeds that it won't work ... this is the current version of vtd-xml encoding... attribute value has a limit of 1MB.... > On November 1, 2018 at 9:30 AM Erik Fäßler <eri...@un...> wrote: > > > Hi Jimmy, > > I wrote a nice program using VTD-XML and and I am - as most of the time - very happy with it. > But now I was using some larger documents with it. The issue is - I think - that the XML format I have given (UIMA XMI format) stores multiple MB of string data in one attribute. This seems to cause the error > > com.ximpleware.extended.ParseExceptionHuge: Token Length Error: Attr val too long (>0xfffff) > > Now I was wondering why the maximum size of the tokens is that small. I know that for most XML documents that should suffice but in the case of UIMA XMI it can easily be exceeded. > Would it be possible to just raise this limit? Perhaps make it configurable? > > Thanks, > > Erik_______________________________________________ > Vtd-xml-users mailing list > Vtd...@li... > https://lists.sourceforge.net/lists/listinfo/vtd-xml-users |
|
From: Erik F. <eri...@un...> - 2018-11-01 14:30:38
|
Hi Jimmy, I wrote a nice program using VTD-XML and and I am - as most of the time - very happy with it. But now I was using some larger documents with it. The issue is - I think - that the XML format I have given (UIMA XMI format) stores multiple MB of string data in one attribute. This seems to cause the error com.ximpleware.extended.ParseExceptionHuge: Token Length Error: Attr val too long (>0xfffff) Now I was wondering why the maximum size of the tokens is that small. I know that for most XML documents that should suffice but in the case of UIMA XMI it can easily be exceeded. Would it be possible to just raise this limit? Perhaps make it configurable? Thanks, Erik |
|
From: Jimmy Z. <jz...@xi...> - 2018-02-15 23:08:16
|
Thanks will look into it...
----- Original Message -----
From: "Owen Sam Springer UK"
To:"vtd...@li..."
Cc:
Sent:Thu, 1 Feb 2018 12:41:43 +0000
Subject:[Vtd-xml-users] Weird edge case with element fragment and PI
Hi,
I've come across what I believe is a bug when processing instructions
are included. Here's a test case.
Thanks,
Sam
import com.ximpleware.* [1];
import org.junit.Assert [2];
import org.junit [3].Test;
public class PIBugTest {
@Test
public void getElementFragmentTooLongWhenPIAndCarrageReturn() throws
XPathParseException, NavException, XPathEvalException, ParseException
{
String exampleXml =
"n" +
" valuen" +
" hellon" +
" n" +
" another valuen" +
"n";
VTDGen vg = new VTDGen();
vg.setDoc(exampleXml.getBytes()) [4];
vg.parse( [5]false);
VTDNav nav = vggetNav() [6];
AutoPilot autoPilot = new AutoPilot(nav);
autoPilot.selectXPath( [7]"/a//b");
autoPilot.evalXPath() [8];
long fragment = nav.getElementFragment() [9];
IByteBuffer xml = nav.getXML() [10];
int offset = (int) fragment;
int len = (int) (fragment >>> 32);
//Fix for weird bug with pi
Assert.assertEquals(new String(xml.getBytes() [11], offset, len),
"value");
}
}
DISCLAIMER: This e-mail is confidential and should not be used by
anyone who is not the original intended recipient. If you have
received this e-mail in error please inform the sender and delete it
from your mailbox or any other storage mechanism. Springer-Verlag
London Limited does not accept liability for any statements made which
are clearly the sender's own and not expressly made on behalf of
Springer-Verlag London Limited or one of their agents.
Please note that Springer-Verlag London Limited and their agents and
affiliates do not accept any responsibility for viruses or malware
that may be contained in this e-mail or its attachments and it is your
responsibility to scan the e-mail and attachments (if any).
Springer-Verlag London Limited. Registered office: The Campus, 4
Crinan Street, London, N1 9XW. Registered Number: 01738860 England.
Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://org.junit.Assert
[3] http://org.junit
[4] http://sitemail.hostway.com/http:
[5] http://sitemail.hostway.com/http:
[6] http://sitemail.hostway.com/http:
[7] http://sitemail.hostway.com/http:
[8] http://sitemail.hostway.com/http:
[9] http://sitemail.hostway.com/http:
[10] http://sitemail.hostway.com/http:
[11] http://sitemail.hostway.com/http:
|
|
From: Owen, S. S. U. <sam...@sp...> - 2018-02-01 13:16:58
|
??Hi,
I've come across what I believe is a bug when processing instructions are included. Here's a test case.
Thanks,
Sam
import com.ximpleware.*;
import org.junit.Assert;
import org.junit.Test;
public class PIBugTest {
@Test
public void getElementFragmentTooLongWhenPIAndCarrageReturn() throws XPathParseException, NavException, XPathEvalException, ParseException {
String exampleXml =
"<a>\n" +
" <b>value</b>\n" +
" hello\n" +
" <?pi inst $pi#?>\n" +
" <b>another value</b>\n" +
"</a>\n";
VTDGen vg = new VTDGen();
vg.setDoc(exampleXml.getBytes());
vg.parse(false);
VTDNav nav = vg.getNav();
AutoPilot autoPilot = new AutoPilot(nav);
autoPilot.selectXPath("/a//b");
autoPilot.evalXPath();
long fragment = nav.getElementFragment();
IByteBuffer xml = nav.getXML();
int offset = (int) fragment;
int len = (int) (fragment >>> 32);
//Fix for weird bug with pi
Assert.assertEquals(new String(xml.getBytes(), offset, len), "<b>value</b>");
}
}
?
DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Springer-Verlag London Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Springer-Verlag London Limited or one of their agents.
Please note that Springer-Verlag London Limited and their agents and affiliates do not accept any responsibility for viruses or malware that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any).
Springer-Verlag London Limited. Registered office: The Campus, 4 Crinan Street, London, N1 9XW. Registered Number: 01738860 England.
|
|
From: Jimmy Z. <jz...@xi...> - 2017-09-02 02:49:41
|
The reason that you are getting that error message is because somewhere in the XML file a namespace prefix isn't backed by its URL declaration...that tells me that you are not either insert into places where the element is not under the umbrella of the namespace declaration... so you may have to do it by hand... that is the advice I can provide without looking at the original xml file and the element you want to insert into it.. ----- Original Message ----- From: W K To:"vtd...@li..." Cc: Sent:Fri, 1 Sep 2017 22:23:29 +0000 Subject:[Vtd-xml-users] Inserting XML content as a child element When inserting XML content as a child element (element names do have namespace prefixes), is it necessary for the inserted content to contain namespace declarations, even though the target document already has them in the root element? I am getting the following error when trying to insert: com.ximpleware.ParseException: [1] Name space qualification Exception: Element not qualified I am using v2.11, and not able to upgrade at this time. Links: ------ [1] http://com.ximpleware.ParseException |
|
From: W K <wka...@ho...> - 2017-09-01 22:23:37
|
When inserting XML content as a child element (element names do have namespace prefixes), is it necessary for the inserted content to contain namespace declarations, even though the target document already has them in the root element? I am getting the following error when trying to insert: com.ximpleware.ParseException: Name space qualification Exception: Element not qualified I am using v2.11, and not able to upgrade at this time. |
|
From: Jan N. <Jan...@iv...> - 2017-07-25 07:56:25
|
Good idea, I've edited my answer with some clarification. Jan. ________________________________ Van: Jimmy Zhang [jz...@xi...] Verzonden: maandag 24 juli 2017 21:05 To: Jan Niestadt; vtd...@li... Onderwerp: Re: [Vtd-xml-users] Dynamic lookup using only XPath Nice to hear that. Hope you can post it to the SO website so others can benefit from this... ----- Original Message ----- From: Jan Niestadt <Jan...@iv...> To: "vtd...@li..." <vtd...@li...> Cc: Sent: Mon, 24 Jul 2017 07:59:56 +0000 Subject: Re: [Vtd-xml-users] Dynamic lookup using only XPath Hi, Just to follow up on this: I asked this question on Stack Overflow as well, see https://stackoverflow.com/questions/45191706/dynamic-lookup-in-vtd-xml-using-only-xpath. Unfortunately, what I was looking for is not possible directly. I solved it by implementing a very basic variable substitution system myself. Best, Jan Niestadt. ________________________________ Van: Jan Niestadt Verzonden: woensdag 19 juli 2017 15:00 To: vtd...@li...<mailto:vtd...@li...> Onderwerp: Dynamic lookup using only XPath Hi, I'm trying to use an XPath expression to find elements referring to the current element in VTD-XML. So say my XML contains books and ratings and looks like this: <root> <book id="1" name="Book1"/> <book id="2" name="Book1"/> <rating book-id="1" value="5"/> <rating book-id="2" value="3"/> </root> First I'm iterating over all book elements. Then, for each book, I want to execute an XPath expression that fetches the rating for that book. For example: /root/rating[@book-id=current()/@id]/@value This doesn't work as the current() function is exclusive to XSLT. So I tried declaring a variable expression named "current" to "." to mean "the current book", but that doesn't work either because (as the name implies), a variable expression doesn't store the results of the expression, but the expression itself. Is there a way to achieve this effect in VTD-XML using just an XPath expression? (I realize there's various ways of doing it in Java code, but I want to use pure XPath so users can easily create a configuration file describing their data format) Thanks for any suggestions! Best, Jan Niestadt. ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ---------------------------------------------------------- ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ---------------------------------------------------------- |
|
From: Jimmy Z. <jz...@xi...> - 2017-07-24 19:15:42
|
Nice to hear that. Hope you can post it to the SO website so others can benefit from this... ----- Original Message ----- From: Jan Niestadt To:"vtd...@li..." Cc: Sent:Mon, 24 Jul 2017 07:59:56 +0000 Subject:Re: [Vtd-xml-users] Dynamic lookup using only XPath Hi, Just to follow up on this: I asked this question on Stack Overflow as well, see https://stackoverflow.com/questions/45191706/dynamic-lookup-in-vtd-xml-using-only-xpath [1]. Unfortunately, what I was looking for is not possible directly. I solved it by implementing a very basic variable substitution system myself. Best, Jan Niestadt. ------------------------- VAN: Jan Niestadt VERZONDEN: woensdag 19 juli 2017 15:00 TO: vtd...@li... [2] ONDERWERP: Dynamic lookup using only XPath Hi, I'm trying to use an XPath expression to find elements referring to the current element in VTD-XML. So say my XML contains books and ratings and looks like this: First I'm iterating over all book elements. Then, for each book, I want to execute an XPath expression that fetches the rating for that book. For example: /root/rating[@book-id=current()/@id]/@value This doesn't work as the current() function is exclusive to XSLT. So I tried declaring a variable expression named "current" to "." to mean "the current book", but that doesn't work either because (as the name implies), a variable expression doesn't store the results of the expression, but the expression itself. Is there a way to achieve this effect in VTD-XML using just an XPath expression? (I realize there's various ways of doing it in Java code, but I want to use pure XPath so users can easily create a configuration file describing their data format) Thanks for any suggestions! Best, Jan Niestadt. ------------------------- ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ---------------------------------------------------------- Links: ------ [1] https://stackoverflow.com/questions/45191706/dynamic-lookup-in-vtd-xml-using-only-xpath [2] mailto:vtd...@li... |
|
From: Jan N. <Jan...@iv...> - 2017-07-24 08:00:08
|
Hi, Just to follow up on this: I asked this question on Stack Overflow as well, see https://stackoverflow.com/questions/45191706/dynamic-lookup-in-vtd-xml-using-only-xpath. Unfortunately, what I was looking for is not possible directly. I solved it by implementing a very basic variable substitution system myself. Best, Jan Niestadt. ________________________________ Van: Jan Niestadt Verzonden: woensdag 19 juli 2017 15:00 To: vtd...@li... Onderwerp: Dynamic lookup using only XPath Hi, I'm trying to use an XPath expression to find elements referring to the current element in VTD-XML. So say my XML contains books and ratings and looks like this: <root> <book id="1" name="Book1"/> <book id="2" name="Book1"/> <rating book-id="1" value="5"/> <rating book-id="2" value="3"/> </root> First I'm iterating over all book elements. Then, for each book, I want to execute an XPath expression that fetches the rating for that book. For example: /root/rating[@book-id=current()/@id]/@value This doesn't work as the current() function is exclusive to XSLT. So I tried declaring a variable expression named "current" to "." to mean "the current book", but that doesn't work either because (as the name implies), a variable expression doesn't store the results of the expression, but the expression itself. Is there a way to achieve this effect in VTD-XML using just an XPath expression? (I realize there's various ways of doing it in Java code, but I want to use pure XPath so users can easily create a configuration file describing their data format) Thanks for any suggestions! Best, Jan Niestadt. ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ---------------------------------------------------------- |
|
From: Jan N. <Jan...@iv...> - 2017-07-19 13:31:41
|
Hi, I'm trying to use an XPath expression to find elements referring to the current element in VTD-XML. So say my XML contains books and ratings and looks like this: <root> <book id="1" name="Book1"/> <book id="2" name="Book1"/> <rating book-id="1" value="5"/> <rating book-id="2" value="3"/> </root> First I'm iterating over all book elements. Then, for each book, I want to execute an XPath expression that fetches the rating for that book. For example: /root/rating[@book-id=current()/@id]/@value This doesn't work as the current() function is exclusive to XSLT. So I tried declaring a variable expression named "current" to "." to mean "the current book", but that doesn't work either because (as the name implies), a variable expression doesn't store the results of the expression, but the expression itself. Is there a way to achieve this effect in VTD-XML using just an XPath expression? (I realize there's various ways of doing it in Java code, but I want to use pure XPath so users can easily create a configuration file describing their data format) Thanks for any suggestions! Best, Jan Niestadt. ________________________________ ---------------------------------------------------------- Aan dit bericht kunnen geen rechten worden ontleend. Het bericht is alleen bestemd voor de geadresseerde. Indien het bericht niet voor u is bestemd, verzoeken wij u dit aan ons te melden en het bericht te verwijderen. This message shall not constitute any obligations. This message is intended solely for the addressee. If you have received this message in error, please inform us and delete the message. ---------------------------------------------------------- |
|
From: Suphatsara P. <sup...@gm...> - 2017-05-02 11:00:37
|
|
From: Thamm, R. <Rus...@ds...> - 2017-05-02 01:25:47
|
UNCLASSIFIED
Hi Jimmy,
I bit the bullet and converted my software to use your C++ library (32 bit). I was using an old version of your C library with my own C++ wrapper.
It all seems to work OK.
However Visual Leak Detector reports a large number of 64 byte memory leaks.
I am including a code fragment in case I am doing something wrong.
bool CPropertyDocument::hasProperty(const std::string &propName)
{
unsigned short wcstr[200];
size_t len;
mbstowcs_s(&len, (wchar_t *)wcstr, 200, propName.c_str(), propName.size());
wcstr[len] = 0;
wchar_t qry[200];
wcscpy_s((wchar_t *)qry,200,L"//property[@id='");
wcsncat_s((wchar_t *)qry,200,(wchar_t *)wcstr,len);
wcscat_s((wchar_t *)qry,200,L"']");
ap->selectXPath(qry);
int result = ap->evalXPath();
ap->resetXPath();
if (result == -1)
{
return false;
}
return true;
}
Output from VLD
---------- Block 3980 at 0x001C0610: 64 bytes ----------
Call Stack:
c:\thirdpartylibs\cpp\ximpleware-2.12-c++\vtd-xml\xpathparser.yy (302): yy::xpathParser::parse
c:\thirdpartylibs\cpp\ximpleware-2.12-c++\vtd-xml\xpath_driver.cc (60): xpath_driver::parse
c:\thirdpartylibs\cpp\ximpleware-2.12-c++\vtd-xml\autopilot.cpp (525): com_ximpleware::AutoPilot::selectXPath
c:\myprojects\msvc\hil\subsystem\rtobject\propertydocument.cpp (182): CPropertyDocument::hasProperty
I get similar for all calls to selectXPath.
Am I doing something wrong?
Cheers
Russell
IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.
|
|
From: Erik F. <eri...@un...> - 2017-03-30 06:11:32
|
Well, you have to care at least for text tokens and sibling elements. That is, to know if you have left an element you must do something like
(vn.getTokenType(index) == VTDNav.TOKEN_STARTING_TAG && vn.getTokenDepth(index) <= elementDepth) || vn.getTokenDepth(index) < elementDepth
while this is certainly doable, it took some time to figure it out and is still way more complicated than other APIs. Perhaps it would be helpful to remove the TOKEN_ENDING_TAG constant, because it is confusing, and add a method for element ending detection in the above spirit.
> On 29 Mar 2017, at 21:03, Jimmy Zhang <jz...@xi...> wrote:
>
> it is not kept by the xml parser in order to reduce memory requirement... basically, after start and ending element is done, ending tag serves no significant purpose..
> in fact, the combination of token depth is sufficient to indicate the location in the document... I don't think that part is ambiguous ...
>
>
>
> ----- Original Message -----
> From:
> Erik Fäßler <eri...@un...>
>
> To:
> "Nil Ratan Sahoo" <nil...@ya...>
> Cc:
> "vtd...@li..." <vtd...@li...>
> Sent:
> Tue, 28 Mar 2017 16:13:08 +0200
> Subject:
> Re: [Vtd-xml-users] VTD 2.13.1: No TOKEN_ENDING_TAG tokens
>
>
> Hi again,
>
> I’m afraid the combination of TOKEN_STARTING_TAG and depth is ambiguously. Text tokens and property tokens (e.g. TOKEN_PI_NAME) have the same depth as the element starting tag.
> To have explicit TOKEN_ENDING_TAG tokens would be really helpful and enhance the usability of VTD-XML a lot. I am fighting half the day for reliable way to tell whether I’m still in a specific element or not. I will make it eventually, but by now I wished I would just have used StAX. I would have finished hours ago if I had. Actually I’m thinking of changing to StAX right now, might be quicker…
>
> Best,
>
> Erik
>
> On 27 Mar 2017, at 19:39, Nil Ratan Sahoo <nil...@ya... <mailto:nil...@ya...>> wrote:
>
> Hi Erik,
>
> By default VTDNav.TOKEN_ENDING_TAG is not part of index, you can use VTDNav.TOKEN_STARTING_TAG and depth to determine end of a tag.
>
> thanks
> Nil
>
>
> On Monday, 27 March 2017 8:01 AM, Erik Fäßler <eri...@un... <mailto:eri...@un...>> wrote:
>
>
> Hi Jimmy,
>
> I am currently building a program using VTD that parses the XML document element-wise. That means that when a TOKEN_START_TAG token is encountered, a specific class is called that processes the current element. For this, the called class iterates over the tokens until it finds the end of the element. I thought I could just wait for a TOKEN_ENDING_TAG token and check if it matches the original TOKEN_START_TAG and the token depth of the start token. However, it seams that absolutely no token is of type TOKEN_ENDING_TAG in the whole document. My code:
>
> for (int i = vn.getCurrentIndex(); i < vn.getTokenCount(); i++) {
> System.out.println(i);
> if (vn.getTokenType(i) == VTDNav.TOKEN_ENDING_TAG)
> {
> System.out.println("Ending token found!");
> System.out.println(vn.toString(i));
> break;
> }
> }
>
>
> This code never prints out the “Ending token found!” line. It just counts through all tokens up to vn.getTokenCount().
>
> Am I doing something wrong?
>
> Thanks!
>
> Best regards,
>
> Erik
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________
> Vtd-xml-users mailing list
> Vtd...@li... <mailto:Vtd...@li...>
> https://lists.sourceforge.net/lists/listinfo/vtd-xml-users <https://lists.sourceforge.net/lists/listinfo/vtd-xml-users>
>
>
>
|
|
From: Jimmy Z. <jz...@xi...> - 2017-03-29 19:22:11
|
it is not kept by the xml parser in order to reduce memory
requirement... basically, after start and ending element is done,
ending tag serves no significant purpose..in fact, the combination of
token depth is sufficient to indicate the location in the document...
I don't think that part is ambiguous ...
----- Original Message -----
From: Erik Fäßler
To:"Nil Ratan Sahoo"
Cc:"vtd...@li..."
Sent:Tue, 28 Mar 2017 16:13:08 +0200
Subject:Re: [Vtd-xml-users] VTD 2.13.1: No TOKEN_ENDING_TAG tokens
Hi again,
I’m afraid the combination of TOKEN_STARTING_TAG and depth is
ambiguously. Text tokens and property tokens (e.g. TOKEN_PI_NAME) have
the same depth as the element starting tag.To have explicit
TOKEN_ENDING_TAG tokens would be really helpful and enhance the
usability of VTD-XML a lot. I am fighting half the day for reliable
way to tell whether I’m still in a specific element or not. I will
make it eventually, but by now I wished I would just have used StAX. I
would have finished hours ago if I had. Actually I’m thinking of
changing to StAX right now, might be quicker…
Best,
Erik
On 27 Mar 2017, at 19:39, Nil Ratan Sahoo wrote:
Hi Erik,
By default VTDNav.TOKEN_ENDING_TAG is not part of index, you can
use VTDNav.TOKEN_STARTING_TAG and depth to determine end of a tag.
thanksNil
On Monday, 27 March 2017 8:01 AM, Erik Fäßler wrote:
Hi Jimmy,
I am currently building a program using VTD that parses the XML
document element-wise. That means that when a TOKEN_START_TAG token is
encountered, a specific class is called that processes the current
element. For this, the called class iterates over the tokens until it
finds the end of the element. I thought I could just wait for a
TOKEN_ENDING_TAG token and check if it matches the original
TOKEN_START_TAG and the token depth of the start token. However, it
seams that absolutely no token is of type TOKEN_ENDING_TAG in the
whole document. My code:
for (int i = vn.getCurrentIndex(); i < vn.getTokenCount(); i++) {
System.out.println(i); if (vn.getTokenType(i) ==
VTDNav.TOKEN_ENDING_TAG) { System.out.println("Ending token found!");
System.out.println(vn.toString(i)); break; } }
This code never prints out the “Ending token found!” line. It just
counts through all tokens up to vn.getTokenCount().
Am I doing something wrong?
Thanks!
Best regards,
Erik------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org [3]! http://sdm.link/slashdot
[4]_______________________________________________
Vtd-xml-users mailing list
Vtd...@li...urceforgenet [5]
https://lists.sourceforge.net/lists/listinfo/vtd-xml-users [6]
Links:
------
[1] mailto:nil...@ya...
[2] mailto:eri...@un...
[3] http://slashdot.org
[4] http://sdm.link/slashdot
[5] mailto:Vtd...@li...
[6] https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
|
|
From: Erik F. <eri...@un...> - 2017-03-28 14:13:18
|
Hi again,
I’m afraid the combination of TOKEN_STARTING_TAG and depth is ambiguously. Text tokens and property tokens (e.g. TOKEN_PI_NAME) have the same depth as the element starting tag.
To have explicit TOKEN_ENDING_TAG tokens would be really helpful and enhance the usability of VTD-XML a lot. I am fighting half the day for reliable way to tell whether I’m still in a specific element or not. I will make it eventually, but by now I wished I would just have used StAX. I would have finished hours ago if I had. Actually I’m thinking of changing to StAX right now, might be quicker…
Best,
Erik
> On 27 Mar 2017, at 19:39, Nil Ratan Sahoo <nil...@ya...> wrote:
>
> Hi Erik,
>
> By default VTDNav.TOKEN_ENDING_TAG is not part of index, you can use VTDNav.TOKEN_STARTING_TAG and depth to determine end of a tag.
>
> thanks
> Nil
>
>
> On Monday, 27 March 2017 8:01 AM, Erik Fäßler <eri...@un...> wrote:
>
>
> Hi Jimmy,
>
> I am currently building a program using VTD that parses the XML document element-wise. That means that when a TOKEN_START_TAG token is encountered, a specific class is called that processes the current element. For this, the called class iterates over the tokens until it finds the end of the element. I thought I could just wait for a TOKEN_ENDING_TAG token and check if it matches the original TOKEN_START_TAG and the token depth of the start token. However, it seams that absolutely no token is of type TOKEN_ENDING_TAG in the whole document. My code:
>
> for (int i = vn.getCurrentIndex(); i < vn.getTokenCount(); i++) {
> System.out.println(i);
> if (vn.getTokenType(i) == VTDNav.TOKEN_ENDING_TAG)
> {
> System.out.println("Ending token found!");
> System.out.println(vn.toString(i));
> break;
> }
> }
>
>
> This code never prints out the “Ending token found!” line. It just counts through all tokens up to vn.getTokenCount().
>
> Am I doing something wrong?
>
> Thanks!
>
> Best regards,
>
> Erik
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________
> Vtd-xml-users mailing list
> Vtd...@li... <mailto:Vtd...@li...>
> https://lists.sourceforge.net/lists/listinfo/vtd-xml-users <https://lists.sourceforge.net/lists/listinfo/vtd-xml-users>
>
>
|
|
From: Nil R. S. <nil...@ya...> - 2017-03-27 18:00:20
|
Hi Erik,
By default VTDNav.TOKEN_ENDING_TAG is not part of index, you can use VTDNav.TOKEN_STARTING_TAG and depth to determine end of a tag.
thanksNil
On Monday, 27 March 2017 8:01 AM, Erik Fäßler <eri...@un...> wrote:
Hi Jimmy,
I am currently building a program using VTD that parses the XML document element-wise. That means that when a TOKEN_START_TAG token is encountered, a specific class is called that processes the current element. For this, the called class iterates over the tokens until it finds the end of the element. I thought I could just wait for a TOKEN_ENDING_TAG token and check if it matches the original TOKEN_START_TAG and the token depth of the start token. However, it seams that absolutely no token is of type TOKEN_ENDING_TAG in the whole document. My code:
for (int i = vn.getCurrentIndex(); i < vn.getTokenCount(); i++) { System.out.println(i); if (vn.getTokenType(i) == VTDNav.TOKEN_ENDING_TAG) { System.out.println("Ending token found!"); System.out.println(vn.toString(i)); break; } }
This code never prints out the “Ending token found!” line. It just counts through all tokens up to vn.getTokenCount().
Am I doing something wrong?
Thanks!
Best regards,
Erik------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Vtd-xml-users mailing list
Vtd...@li...
https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
|
|
From: Erik F. <eri...@un...> - 2017-03-27 14:59:06
|
Hi Jimmy,
I am currently building a program using VTD that parses the XML document element-wise. That means that when a TOKEN_START_TAG token is encountered, a specific class is called that processes the current element. For this, the called class iterates over the tokens until it finds the end of the element. I thought I could just wait for a TOKEN_ENDING_TAG token and check if it matches the original TOKEN_START_TAG and the token depth of the start token. However, it seams that absolutely no token is of type TOKEN_ENDING_TAG in the whole document. My code:
for (int i = vn.getCurrentIndex(); i < vn.getTokenCount(); i++) {
System.out.println(i);
if (vn.getTokenType(i) == VTDNav.TOKEN_ENDING_TAG)
{
System.out.println("Ending token found!");
System.out.println(vn.toString(i));
break;
}
}
This code never prints out the “Ending token found!” line. It just counts through all tokens up to vn.getTokenCount().
Am I doing something wrong?
Thanks!
Best regards,
Erik |
|
From: Jimmy Z. <jz...@xi...> - 2016-10-26 05:58:04
|
Can you send me the c++ code so I can examine and critique? ----- Original Message ----- From: "Thamm Russell" To:"vtd...@li..." Cc: Sent:Wed, 26 Oct 2016 02:32:52 +0000 Subject:[Vtd-xml-users] 64 bit issues [SEC=UNCLASSIFIED] UNCLASSIFIED Is vtd-xml C++ usable in 64 bit programs? I have been using the c version in my code but when I compile my application for 64 bit, freeAutoPilot crashes. So, I downloaded the latest C++ version and compiled it for 64 bit. When I run the testNodeRecorder example, it crashes in “delete vn”. vtdNav.cpp [1] line 1243 h1 = 0xcdcdcdcd. I set h1 & h2 to NULL in the constructor and now the example runs. But I suspect there are more issues. BTW, the newpo.xml [2] file is not valid xml. I edited it to make it valid. Unfortunately, my work is blocking access to all of your doco. Cheers Russell IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. Links: ------ [1] http://vtdNav.cpp [2] http://newpo.xml |
|
From: Thamm, R. <rus...@ds...> - 2016-10-26 02:32:22
|
UNCLASSIFIED Is vtd-xml C++ usable in 64 bit programs? I have been using the c version in my code but when I compile my application for 64 bit, freeAutoPilot crashes. So, I downloaded the latest C++ version and compiled it for 64 bit. When I run the testNodeRecorder example, it crashes in "delete vn". vtdNav.cpp line 1243 h1 = 0xcdcdcdcd. I set h1 & h2 to NULL in the constructor and now the example runs. But I suspect there are more issues. BTW, the newpo.xml file is not valid xml. I edited it to make it valid. Unfortunately, my work is blocking access to all of your doco. Cheers Russell IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email. |
|
From: Jimmy Z. <jz...@xi...> - 2016-10-12 03:19:01
|
for now. 2.12 is the most up to date ones... and it seems that few people/enterprises we deal with wanted all platforms at the same time... but will get 2.13 out asap for other platforms ----- Original Message ----- From: al...@sa... To:"Jimmy Zhang" , Cc: Sent:Wed, 5 Oct 2016 12:02:56 -0300 Subject:Re: [Vtd-xml-users] Problems building vtd-xml C# 2.12 It appears there is now a 2.13 version only available in Java. The 2.12 version source code only compiles in Java. As mentioned below in May, the C# and other source code does not build as-is. The code is also not in a condition where someone can just clean it up and make it build. You are leaving your users of the C, C++, and C# languages in a bad place. Lack of support for languages which were supported in the past is killing us - we can't update just the Java platform, so we update none of them. Regards, Al ---------- ORIGINAL MESSAGE ----------- From: Jimmy Zhang To: al...@sa... [2], vtd...@li... [3] Sent: Tue, 31 May 2016 17:05:44 -0500 Subject: Re: [Vtd-xml-users] Problems building vtd-xml C# 2.12 > The source distribution include a few files not really need to build the binary lib... > > .flex and .cup are the files that does the flex and xpath parsing compiler generation... they are the basis for yylex.cs [4] and parser.cs [5]... > some of the files like > > .#FuncExpr.cs.1.28 [6]. > > are old database file for CVS that survived(unfornately) a few rounds of cleanup > > As to pragma's I am not sure the cause of the problems.yet, at least my own build does not exhibit such issues..... > > All other warning should be safely ignored... > > I will try to look into bundling the C# project files ... was a bit hesitate on doing so lest it cause back-compatibility issues for old version of Visual Studios > > Overall, C# of vtd-xml is not as well focused as Java version... > > next version 2.13 will try to clean things up to meet higher standards... > > Thanks for the input > > > ----- Original Message ----- > > From: al...@sa... > > To: > > Cc: > > Sent:Thu, 26 May 2016 13:09:22 -0300 > > Subject:[Vtd-xml-users] Problems building vtd-xml C# 2.12 > > Wanted to update my project from 2.11 to 2.12. > > Downloaded the source for vtd-xml 2.12 from sourceforge and tried to build in VisualStudio 2013 and > Mono 4. > > The build of vtd-xml 2.12 C# fails for a lot of reasons. > > Here are the issues found trying to build vtd-xml 2.12 from source: > - There are source code files with a pattern like .#FuncExpr.cs.1.28 [7]. > They do not compile They appear to be diff or merge results. > - There are other files with .flex, and .cup file extensions. They don't appear to be actual source > code and they don't build. > - All code with pragma warnings comes up as a build error with 'Unknown Number'. The comments around > the warnings don't seem correct, so its hard to know what the correct number should be. > Have to remove all pragma statements to get the code to compile. > - Many classes in com.ximpleware.xpath [8] complain that there is 'no suitable method found to override' > for the isFinal(), markCacheable(), or clearCache() methods. > This is very odd because the problem classes extend an abstract class which does not have the > aforementioned 3 methods. There is no interface, so the abstract class is even more confusing. > - It appears that com.ximpleware [9] source is dependent on TUVienna, which has the same issues with the > source code as vtd-xml. > > QUESTIONS about building vtd-xml 2.12: > > 1. Is the source code supposed to be in this condition? > Seems like its not really 'release ready'. > 2. If the C# source won't build without heavy modification, does that mean it was never tested > before it was released? > 3. How would you suggest resolving the problem with the xpath classes? I want my version of vtd-xml > to match what you intended to release. > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j [10] > _______________________________________________ > Vtd-xml-users mailing list > Vtd...@li... [11] > https://lists.sourceforge.net/lists/listinfo/vtd-xml-users [12] > ------- END OF ORIGINAL MESSAGE ------- Links: ------ [1] mailto:jz...@xi... [2] mailto:al...@sa... [3] mailto:vtd...@li... [4] http://yylex.cs [5] http://parser.cs [6] http:/// [7] http:/// [8] http://com.ximpleware.xpath/ [9] http://com.ximpleware/ [10] https://ad.doubleclick.net/ddm/clk/304595813;131938128;j [11] mailto:Vtd...@li... [12] https://lists.sourceforge.net/lists/listinfo/vtd-xml-users |
|
From: Nil R. S. <nil...@ya...> - 2016-10-05 20:49:49
|
try this approach
public List<String> evaluateToNodeList(String xp, VTDNav vn) throws Exception { List<String> lns = new ArrayList<String>(); AutoPilot ap = new AutoPilot(vn); ap.selectXPath(xp); int curr = vn.getCurrentIndex(); while (ap.evalXPath() != -1) { lns.add(getValue(vn, vn.getCurrentIndex())); } vn.recoverNode(curr); ap.resetXPath();
return lns; }
public String getValue(VTDNav vNode, int cur) { String value = null; // This is to restore back VTDNav if we re use across different objects. int _cur = vNode.getCurrentIndex(); try { vNode.recoverNode(cur); vNode.push(); /* * extracting entire all text content of node (along with child nodes text) */ if (vNode.getTokenType(cur) == VTDNav.TOKEN_STARTING_TAG) { value = vNode.getXPathStringVal(); } else if (vNode.getTokenType(cur) == VTDNav.TOKEN_ATTR_NAME) { value = vNode.toNormalizedString(cur + 1); } else { int t = vNode.getText(); // get the index of the text (char data or CDATA) if (t != -1) { value = vNode.toNormalizedString(t); } } } catch (NavException e) {
}
// This is to restore back VTDNav if we re use across different objects. try { vNode.recoverNode(_cur); } catch (Exception e) { } return value; }
On Wednesday, 5 October 2016 8:09 AM, "al...@sa..." <al...@sa...> wrote:
Is there a way to avoid having to call setDoc and parse each time we need to use VTDNav?
We want to create one VTDGen object per XML document and re-use it for xpath queries.
Right now, we are loading the VTDGen object each time we need to run a query, like this:
VTDGen vtdGen = new VTDGen();
vtdGen.setDoc(xmlBytes);
vtdGen.parse(false);
VTDNav vtdNav = vtdGen.getNav();
Instead, we would like to pass the vtdGen object to different methods and not call setDoc() and
parse() every time.
The problem occurs with VTDNav - it seems that it must be created right after calling VTDGen.parse().
Otherwise we get an exception "Value does not fall within the selected range" when using vtdGen.getNav()
We are using VTDXML 2.11 in C# and Java. (because v2.12 only works with Java)
Thanks,
Al
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Vtd-xml-users mailing list
Vtd...@li...
https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
|
|
From: <al...@sa...> - 2016-10-05 15:07:10
|
Is there a way to avoid having to call setDoc and parse each time we need to use VTDNav? We want to create one VTDGen object per XML document and re-use it for xpath queries. Right now, we are loading the VTDGen object each time we need to run a query, like this: VTDGen vtdGen = new VTDGen(); vtdGen.setDoc(xmlBytes); vtdGen.parse(false); VTDNav vtdNav = vtdGen.getNav(); Instead, we would like to pass the vtdGen object to different methods and not call setDoc() and parse() every time. The problem occurs with VTDNav - it seems that it must be created right after calling VTDGen.parse(). Otherwise we get an exception "Value does not fall within the selected range" when using vtdGen.getNav() We are using VTDXML 2.11 in C# and Java. (because v2.12 only works with Java) Thanks, Al |
28 messages has been excluded from this view by a project administrator.
