vtd-xml-users — This mailing list is for users or people interested in VTD-XML

Re: [Vtd-xml-users] Problems building vtd-xml C# 2.12

[<al...@sa...>]

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 <jz...@xi...> 
To: al...@sa..., vtd...@li... 
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 and parser.cs...
> some of the files like
> 
>  .#FuncExpr.cs.1.28.
> 
> 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:<vtd...@li...>
> 
> 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.
> 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 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 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
> _______________________________________________
> Vtd-xml-users mailing list
> Vtd...@li...
> https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
> 
------- End of Original Message -------
 

Re: [Vtd-xml-users] Problems building vtd-xml C# 2.12

[Jimmy Z. <jz...@xi...>]

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 yylexcs and
parser.cs...some of the files like
 .#FuncExpr.cs.1.28 [1].
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
[2].
 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 [3] 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 [4] 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 [5]
 _______________________________________________
 Vtd-xml-users mailing list
Vtd...@li... [6]
https://lists.sourceforge.net/lists/listinfo/vtd-xml-users [7]


Links:
------
[1] http://sitemail.hostway.com/http:/
[2] http://sitemail.hostway.com/http:
[3] http://com.ximpleware.xpath
[4] http://com.ximpleware
[5] https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
[6] mailto:Vtd...@li...
[7] https://lists.sourceforge.net/lists/listinfo/vtd-xml-users

[Vtd-xml-users] Problems building vtd-xml C# 2.12

[<al...@sa...>]

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.
  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 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 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.

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

An updated VTD-XML version 2.12 release has been uploaded... there has
been some missing classes due to source code target issue in the
build.bat file... Please go visit the vtd-xml web site and download
the latest update... I apologize for the SNAFU

----- Original Message -----
From: Jimmy Zhang 
To:, "Jimmy Zhang" , "Suresh Naidu" 
Cc:
Sent:Wed, 04 May 2016 14:17:31 -0500
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

 v2.13 will introduce more methods that allows more control over the
modification output... will come out pretty soon 

----- Original Message -----
From: al...@sa... [1]
To:"Jimmy Zhang" , "Suresh Naidu" 
Cc:
Sent:Tue, 3 May 2016 10:33:00 -0300
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

We assumed vtd-xml was just a fast XML parser, so we used other
tools/apis to format the XML and control whitespaces. 

We take the bytes from vtdnav.getXML().getBytes() and pass them to a
stream to be 
used with javax.xml.transform.Transformer [5]. 
The Transformer allows you to set properties to control indentation
and 
effectively takes out the whitespace you see with vtd-xml. 
It also handles adding newlines, whether they are in the source XML or
not. 
This keeps the formatted xml from being one long line. 

We use vtd-xml to create and parse XML for applications and processes.
Its the best tool for the job. 
We use javax.xml [6] classes to format XML for people and
documentation. 

Regards, 
Al G 

---------- ORIGINAL MESSAGE ----------- 
 From: Jimmy Zhang  
 To: Suresh Naidu , Jimmy Zhang  
 Cc: vtd...@li... [10] 
 Sent: Mon, 02 May 2016 21:49:19 -0500 
 Subject: Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 

> The current implementation of expandWhite space is greedy, it will
eat up all white spaces surrounding the element,  
> 
> more fine-grained control will be introduced in next release of
vtd-xml ...2.13 that is...  
> 
>  
> ----- Original Message ----- 
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sun, 1 May 2016 23:40:42 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dear Zhang, 
> 
> Thanks .I have checked your solution .I agree to you  and I have
posted our discussion ,sample on stack overflow . 
> 
> Still I have a concern,the solution is not fully correct to our
requirement. 
> 
> Input to the program is: 
> 
>  
>    Address1 
>          suresh 
>          Address 
>   Address2 
>  
> 
> Output got: 
> 
>  
>     Address1Address 
>     Address2 
>  
> 
> Output Expected: 
> 
>  
>     Address1 
>             Address 
>     Address2 
>  
> 
> Can this be achievable as we should not change the format of it. 
> 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
>   
> After some polishing I made your code work.. see my attachment, 
> 
> I have a request: would you please post a  question on stack
overflow, so I can respond, and the content of our correspondence can
thus be made available to public and help them as well 
> 
>  
> ----- Original Message ----- 
>  
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sun, 1 May 2016 01:35:36 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dear Zhang, 
> 
> I have tried with expandwhitespaces method with multiple ways,but i
could not get the output. 
> 
> I have not find much examples about its usage. 
> 
> Can you check and let me know if  i am using it correctly or not. 
> 
> I have attached the source code and file used. 
> 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
> Yes, there is, in version 2.12, there is a method called
expandWhiteSpace in VTDNav, it works like the following 
> 
> public final long expandWhiteSpaces(long l) 
> New in v2.12 This method will take a segment descriptor and return a
new descriptor that includes all the leading and trailing white spaces
around the input segment It has no effect on CDATA A typical usage
would be 'expandWhiteSpaces(getElementFragment())'Parameters:l -
upper 32 bits length of the segment, lower 32 bits offset of the
segment, unit is byte offsetReturns:a long 64 bit segment
descriptorThrows:NavException [17]
> 
>  
> ----- Original Message ----- 
>  
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sat, 30 Apr 2016 06:23:38 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Thanks zhang for your reply.It [20] is not a show stopper.but the
requirement from client is to remove that spaces...is there an option
to do that with vtd- xml. 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
> How big a deal is it ? cosmetic or show stopping?  
> 
>  
> ----- Original Message ----- 
> 
> From: Suresh Naidu  
> 
> To: 
> 
> Cc: 
> 
> Sent:Fri, 29 Apr 2016 10:40:39 +0200 
> 
> Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dears, 
> 
> We are using VTD XML for our application.Can [25] you help us in
solving the issue in our application. 
> 
> The issue is: 
> 
> input xml: 
> 
>  
>        suresh 
>        Address 
>  
> 
> output xml: 
>    
>  
> 
>       Address 
>  
> 
> But i want the output to be: 
> 
>  
> 
>       Address 
> 
>  
> 
> When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element. 
> 
> Is there any possibility to remove that vtdxml? 
> 
> Thanks & Regards, 
> G . Suresh Naidu 
> 
>     
>   
>  
------- END OF ORIGINAL MESSAGE ------- 
 

Links:
------
[1] mailto:al...@sa...
[2] mailto:jz...@xi...
[3] mailto:sur...@gm...
[4] mailto:vtd...@li...
[5] http://javax.xml.transform.Transformer
[6] http://javax.xml
[7] mailto:jz...@xi...
[8] mailto:sur...@gm...
[9] mailto:jz...@xi...
[10] mailto:vtd...@li...
[11] mailto:sur...@gm...
[12] mailto:jz...@xi...
[13] mailto:jz...@xi...
[14] mailto:sur...@gm...
[15] mailto:jz...@xi...
[16] mailto:jz...@xi...
[17]
http://vtd-xml.sourceforge.net/javadoc/com/ximpleware/NavException.html
[18] mailto:sur...@gm...
[19] mailto:jz...@xi...
[20] http://reply.it/
[21] http://g.suresh/
[22] mailto:jzhang@ximplewarecom
[23] mailto:sur...@gm...
[24] mailto:vtd...@li...
[25] http://application.can/

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

v2.13 will introduce more methods that allows more control over the
modification output... will come out pretty soon 

----- Original Message -----
From: al...@sa...
To:"Jimmy Zhang" , "Suresh Naidu" 
Cc:
Sent:Tue, 3 May 2016 10:33:00 -0300
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

We assumed vtd-xml was just a fast XML parser, so we used other
tools/apis to format the XML and control whitespaces. 

We take the bytes from vtdnav.getXML().getBytes() [1] and pass them to
a stream to be 
used with javax.xml.transform.Transformer [2]. 
The Transformer allows you to set properties to control indentation
and 
effectively takes out the whitespace you see with vtd-xml. 
It also handles adding newlines, whether they are in the source XML or
not. 
This keeps the formatted xml from being one long line. 

We use vtd-xml to create and parse XML for applications and processes.
Its the best tool for the job. 
We use javax.xml [3] classes to format XML for people and
documentation. 

Regards, 
Al G 

---------- ORIGINAL MESSAGE ----------- 
 From: Jimmy Zhang  
 To: Suresh Naidu , Jimmy Zhang  
 Cc: vtd...@li... [7] 
 Sent: Mon, 02 May 2016 21:49:19 -0500 
 Subject: Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 

> The current implementation of expandWhite space is greedy, it will
eat up all white spaces surrounding the element,  
> 
> more fine-grained control will be introduced in next release of
vtd-xml ...2.13 that is...  
> 
>  
> ----- Original Message ----- 
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sun, 1 May 2016 23:40:42 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dear Zhang, 
> 
> Thanks .I have checked your solution .I agree to you  and I have
posted our discussion ,sample on stack overflow . 
> 
> Still I have a concern,the solution is not fully correct to our
requirement. 
> 
> Input to the program is: 
> 
>  
>    Address1 
>          suresh 
>          Address 
>   Address2 
>  
> 
> Output got: 
> 
>  
>     Address1Address 
>     Address2 
>  
> 
> Output Expected: 
> 
>  
>     Address1 
>             Address 
>     Address2 
>  
> 
> Can this be achievable as we should not change the format of it. 
> 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
>   
> After some polishing I made your code work... see my attachment, 
> 
> I have a request: would you please post a  question on stack
overflow, so I can respond, and the content of our correspondence can
thus be made available to public and help them as well 
> 
>  
> ----- Original Message ----- 
>  
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sun, 1 May 2016 01:35:36 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dear Zhang, 
> 
> I have tried with expandwhitespaces method with multiple ways,but i
could not get the output. 
> 
> I have not find much examples about its usage. 
> 
> Can you check and let me know if  i am using it correctly or not. 
> 
> I have attached the source code and file used. 
> 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
> Yes, there is, in version 2.12, there is a method called
expandWhiteSpace in VTDNav, it works like the following 
> 
> public final long expandWhiteSpaces(long l) 
> New in v2.12 This method will take a segment descriptor and return a
new descriptor that includes all the leading and trailing white spaces
around the input segment It has no effect on CDATA A typical usage
would be 'expandWhiteSpaces(getElementFragment())'Parameters:l -
upper 32 bits length of the segment, lower 32 bits offset of the
segment, unit is byte offsetReturns:a long 64 bit segment
descriptorThrows:NavException [14]
> 
>  
> ----- Original Message ----- 
>  
> 
> From: Suresh Naidu  
> 
> To:"Jimmy Zhang"  
> 
> Cc: 
> 
> Sent:Sat, 30 Apr 2016 06:23:38 +0200 
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Thanks zhang for your reply.It [17] is not a show stopper.but the
requirement from client is to remove that spaces...is there an option
to do that with vtd- xml. 
> Thanks
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex;"
class="gmail_quote"> 
> How big a deal is it ? cosmetic or show stopping?  
> 
>  
> ----- Original Message ----- 
> 
> From: Suresh Naidu  
> 
> To: 
> 
> Cc: 
> 
> Sent:Fri, 29 Apr 2016 10:40:39 +0200 
> 
> Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element 
> 
> Dears, 
> 
> We are using VTD XML for our application.Can [22] you help us in
solving the issue in our application. 
> 
> The issue is: 
> 
> input xml: 
> 
>  
>        suresh 
>        Address 
>  
> 
> output xml: 
>    
>  
> 
>       Address 
>  
> 
> But i want the output to be: 
> 
>  
> 
>       Address 
> 
>  
> 
> When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element. 
> 
> Is there any possibility to remove that vtdxml? 
> 
> Thanks & Regards, 
> G . Suresh Naidu 
> 
>     
>   
>  
------- END OF ORIGINAL MESSAGE ------- 


Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://javax.xml.transform.Transformer
[3] http://javax.xml
[4] mailto:jz...@xi...
[5] mailto:sur...@gm...
[6] mailto:jz...@xi...
[7] mailto:vtd...@li...
[8] mailto:sur...@gm...
[9] mailto:jz...@xi...
[10] mailto:jz...@xi...
[11] mailto:sur...@gm...
[12] mailto:jzhang@ximplewarecom
[13] mailto:jz...@xi...
[14]
http://vtd-xml.sourceforge.net/javadoc/com/ximpleware/NavException.html
[15] mailto:sur...@gm...
[16] mailto:jz...@xi...
[17] http://reply.it/
[18] http://g.suresh/
[19] mailto:jzhang@ximplewarecom
[20] mailto:sur...@gm...
[21] mailto:vtd...@li...
[22] http://application.can/

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[<al...@sa...>]

We assumed vtd-xml was just a fast XML parser, so we used other tools/apis to format the XML and control whitespaces.

We take the bytes from vtdnav.getXML().getBytes() and pass them to a stream to be
used with javax.xml.transform.Transformer. 
The Transformer allows you to set properties to control indentation and
effectively takes out the whitespace you see with vtd-xml.
It also handles adding newlines, whether they are in the source XML or not. 
This keeps the formatted xml from being one long line.

We use vtd-xml to create and parse XML for applications and processes. Its the best tool for the job.
We use javax.xml classes to format XML for people and documentation.

Regards,
Al G

---------- Original Message -----------
From: Jimmy Zhang <jz...@xi...> 
To: Suresh Naidu <sur...@gm...>, Jimmy Zhang <jz...@xi...> 
Cc: vtd...@li... 
Sent: Mon, 02 May 2016 21:49:19 -0500 
Subject: Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

> The current implementation of expandWhite space is greedy, it will eat up all white spaces surrounding the element, 
> 
> more fine-grained control will be introduced in next release of vtd-xml ...2.13 that is... 
> 
> 
> ----- Original Message -----
> 
> From: Suresh Naidu <sur...@gm...>
> 
> To:"Jimmy Zhang" <jz...@xi...>
> 
> Cc:
> 
> Sent:Sun, 1 May 2016 23:40:42 +0200
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element
> 
> Dear Zhang,
> 
> Thanks .I have checked your solution .I agree to you  and I have posted our discussion ,sample on stack overflow .
> 
> Still I have a concern,the solution is not fully correct to our requirement.
> 
> Input to the program is:
> 
> <root>
>    <address1>Address1</address1>
>          <name>suresh</name>
>          <address>Address</address>
>   <address2>Address2</address2>
> </root>
> 
> Output got:
> 
> <root>
>     <address1>Address1</address1><address>Address</address>
>     <address2>Address2</address2>
> </root>
> 
> Output Expected:
> 
> <root>
>     <address1>Address1</address1>
>             <address>Address</address>
>     <address2>Address2</address2>
> </root>
> 
> Can this be achievable as we should not change the format of it.
> 
> Thanks & Regards,
> G. Suresh Naidu
> 
> On Sun, May 1, 2016 at 2:32 AM, Jimmy Zhang <jz...@xi...> wrote:
> 
>  
> After some polishing I made your code work... see my attachment,
> 
> I have a request: would you please post a  question on stack overflow, so I can respond, and the content of our correspondence can thus be made available to public and help them as well
> 
> 
> ----- Original Message -----
> 
> 
> From: Suresh Naidu <sur...@gm...>
> 
> To:"Jimmy Zhang" <jz...@xi...>
> 
> Cc:
> 
> Sent:Sun, 1 May 2016 01:35:36 +0200
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element
> 
> Dear Zhang,
> 
> I have tried with expandwhitespaces method with multiple ways,but i could not get the output.
> 
> I have not find much examples about its usage.
> 
> Can you check and let me know if  i am using it correctly or not.
> 
> I have attached the source code and file used.
> 
> Thanks & Regards,
> G . Suresh Naidu
> 
> On Sat, Apr 30, 2016 at 8:39 PM, Jimmy Zhang <jz...@xi...> wrote:
> 
> Yes, there is, in version 2.12, there is a method called expandWhiteSpace in VTDNav, it works like the following
> 
> public final long expandWhiteSpaces(long l)
> New in v2.12 This method will take a segment descriptor and return a new descriptor that includes all the leading and trailing white spaces around the input segment It has no effect on CDATA A typical usage would be 'expandWhiteSpaces(getElementFragment())'Parameters:l - upper 32 bits length of the segment, lower 32 bits offset of the segment, unit is byte offsetReturns:a long 64 bit segment descriptorThrows:NavException
> 
> 
> ----- Original Message -----
> 
> 
> From: Suresh Naidu <sur...@gm...>
> 
> To:"Jimmy Zhang" <jz...@xi...>
> 
> Cc:
> 
> Sent:Sat, 30 Apr 2016 06:23:38 +0200
> 
> Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element
> 
> Thanks zhang for your reply.It is not a show stopper..but the requirement from client is to remove that spaces...is there an option to do that with vtd- xml.
> Thanks & Regards,
> G.Suresh Naidu
> On Apr 30, 2016 3:00 AM, "Jimmy Zhang" <jz...@xi...> wrote:
> 
> How big a deal is it ? cosmetic or show stopping? 
> 
> 
> ----- Original Message -----
> 
> From: Suresh Naidu <sur...@gm...>
> 
> To:<vtd...@li...>
> 
> Cc:
> 
> Sent:Fri, 29 Apr 2016 10:40:39 +0200
> 
> Subject:[Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element
> 
> Dears,
> 
> We are using VTD XML for our application.Can you help us in solving the issue in our application.
> 
> The issue is:
> 
> input xml:
> 
> <root>
>        <name>suresh</name>
>        <address>Address</address>
> </root>
> 
> output xml:
>   
> <root>
> 
>       <address>Address</address>
> </root>
> 
> But i want the output to be:
> 
> <root>
> 
>       <address>Address</address>
> 
> </root>
> 
> When i remove the element with xmlmodifier it is creating an empty space(new line) for the removed element.
> 
> Is there any possibility to remove that vtdxml?
> 
> Thanks & Regards,
> G . Suresh Naidu
> 
> 
> 
> 
------- End of Original Message -------
 

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

The current implementation of expandWhite space is greedy, it will eat
up all white spaces surrounding the element, 
more fine-grained control will be introduced in next release of
vtd-xml ...2.13 that is... 

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sun, 1 May 2016 23:40:42 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dear Zhang,
Thanks .I have checked your solution .I agree to you  and I have
posted our discussion ,sample on stack overflow .
Still I have a concern,the solution is not fully correct to our
requirement.
Input to the program is:
   Address1         suresh         Address  Address2
Output got:
    Address1Address    Address2
Output Expected:
    Address1            Address    Address2
Can this be achievable as we should not change the format of it.
Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;"> 
After some polishing I made your code work... see my attachment,
I have a request: would you please post a  question on stack
overflow, so I can respond, and the content of our correspondence can
thus be made available to public and help them as well

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sun, 1 May 2016 01:35:36 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dear Zhang,
I have tried with expandwhitespaces method with multiple ways,but i
could not get the output.
I have not find much examples about its usage.
Can you check and let me know if  i am using it correctly or not
I have attached the source code and file used.
Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">Yes,
there is, in version 2.12, there is a method called expandWhiteSpace
in VTDNav, it works like the following

public final long expandWhiteSpaces(long l)New in v2.12 This method
will take a segment descriptor and return a new descriptor that
includes all the leading and trailing white spaces around the input
segment It has no effect on CDATA A typical usage would be
'expandWhiteSpaces(getElementFragment())'Parameters:l - upper 32 bits
length of the segment, lower 32 bits offset of the segment, unit is
byte offsetReturns:a long 64 bit segment descriptorThrows:NavException
[5]

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sat, 30 Apr 2016 06:23:38 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

	Thanks zhang for your reply.It [8] is not a show stopper..but the
requirement from client is to remove that spaces...is there an option
to do that with vtd- xml. 

	Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">How
big a deal is it ? cosmetic or show stopping? 

----- Original Message -----
From: Suresh Naidu 
To:
Cc:
Sent:Fri, 29 Apr 2016 10:40:39 +0200
Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dears,
We are using VTD XML for our application.Can [13] you help us in
solving the issue in our application.
The issue is:
input xml:
       suresh       Address

output xml:  

      Address
But i want the output to be:

      Address

When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element.
Is there any possibility to remove that vtdxml?
Thanks & Regards,G . Suresh Naidu

 

Links:
------
[1] mailto:jz...@xi...
[2] mailto:sur...@gm...
[3] mailto:jz...@xi...
[4] mailto:jz...@xi...
[5]
http://vtd-xml.sourceforge.net/javadoc/com/ximpleware/NavException.html
[6] mailto:sur...@gm...
[7] mailto:jz...@xi...
[8] http://reply.It
[9] http://G.Suresh
[10] mailto:jzhang@ximplewarecom
[11] mailto:sur...@gm...
[12] mailto:vtd...@li...
[13] http://application.Can

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

 
After some polishing I made your code work... see my attachment,
I have a request: would you please post a  question on stack
overflow, so I can respond, and the content of our correspondence can
thus be made available to public and help them as well

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sun, 1 May 2016 01:35:36 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dear Zhang,
I have tried with expandwhitespaces method with multiple ways,but i
could not get the output.
I have not find much examples about its usage.
Can you check and let me know if  i am using it correctly or not
I have attached the source code and file used.
Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">Yes,
there is, in version 2.12, there is a method called expandWhiteSpace
in VTDNav, it works like the following

public final long expandWhiteSpaces(long l)New in v2.12 This method
will take a segment descriptor and return a new descriptor that
includes all the leading and trailing white spaces around the input
segment It has no effect on CDATA A typical usage would be
'expandWhiteSpaces(getElementFragment())'Parameters:l - upper 32 bits
length of the segment, lower 32 bits offset of the segment, unit is
byte offsetReturns:a long 64 bit segment descriptorThrows:NavException
[2]

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sat, 30 Apr 2016 06:23:38 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

	Thanks zhang for your reply.It [5] is not a show stopper..but the
requirement from client is to remove that spaces...is there an option
to do that with vtd- xml. 

	Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">How
big a deal is it ? cosmetic or show stopping? 

----- Original Message -----
From: Suresh Naidu 
To:
Cc:
Sent:Fri, 29 Apr 2016 10:40:39 +0200
Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dears,
We are using VTD XML for our application.Can [10] you help us in
solving the issue in our application.
The issue is:
input xml:
       suresh       Address

output xml:  

      Address
But i want the output to be:

      Address

When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element.
Is there any possibility to remove that vtdxml?
Thanks & Regards,G . Suresh Naidu

 

Links:
------
[1] mailto:jz...@xi...
[2]
http://vtd-xml.sourceforge.net/javadoc/com/ximpleware/NavException.html
[3] mailto:sur...@gm...
[4] mailto:jz...@xi...
[5] http://reply.It
[6] http://G.Suresh
[7] mailto:jzhang@ximplewarecom
[8] mailto:sur...@gm...
[9] mailto:vtd...@li...
[10] http://application.Can

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

Yes, there is, in version 2.12, there is a method called
expandWhiteSpace in VTDNav, it works like the following

	public final long expandWhiteSpaces(long l)New in v2.12 This
method will take a segment descriptor and return a new descriptor that
includes all the leading and trailing white spaces around the input
segment It has no effect on CDATA A typical usage would be
'expandWhiteSpaces(getElementFragment())'Parameters:l - upper 32 bits
length of the segment, lower 32 bits offset of the segment, unit is
byte offsetReturns:a long 64 bit segment descriptorThrows:NavException
[1]

----- Original Message -----
From: Suresh Naidu 
To:"Jimmy Zhang" 
Cc:
Sent:Sat, 30 Apr 2016 06:23:38 +0200
Subject:Re: [Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

	Thanks zhang for your reply.It [2] is not a show stopper..but the
requirement from client is to remove that spaces...is there an option
to do that with vtd- xml. 

	Thanks
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">How
big a deal is it ? cosmetic or show stopping? 

----- Original Message -----
From: Suresh Naidu 
To:
Cc:
Sent:Fri, 29 Apr 2016 10:40:39 +0200
Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dears,
We are using VTD XML for our application.Can [7] you help us in
solving the issue in our application.
The issue is:
input xml:
       suresh       Address

output xml:  

      Address
But i want the output to be:

      Address

When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element.
Is there any possibility to remove that vtdxml?
Thanks & Regards,G . Suresh Naidu

   

Links:
------
[1]
http://vtd-xml.sourceforge.net/javadoc/com/ximpleware/NavException.html
[2] http://reply.It
[3] http://G.Suresh
[4] mailto:jz...@xi...
[5] mailto:sur...@gm...
[6] mailto:vtd...@li...
[7] http://application.Can

Re: [Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Jimmy Z. <jz...@xi...>]

How big a deal is it ? cosmetic or show stopping? 

----- Original Message -----
From: Suresh Naidu 
To:
Cc:
Sent:Fri, 29 Apr 2016 10:40:39 +0200
Subject:[Vtd-xml-users] Suggestion in Removing the spaces after
Removing the Element

Dears,
We are using VTD XML for our application.Can [1] you help us in
solving the issue in our application.
The issue is:
input xml:
       suresh       Address

output xml:  

      Address
But i want the output to be:

      Address

When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element.
Is there any possibility to remove that vtdxml?
Thanks & Regards,G . Suresh Naidu

 

Links:
------
[1] http://application.Can

[Vtd-xml-users] Suggestion in Removing the spaces after Removing the Element

[Suresh N. <sur...@gm...>]

Dears,

We are using VTD XML for our application.Can you help us in solving the
issue in our application.

The issue is:

input xml:

<root>
       <name>suresh</name>
       <address>Address</address>
</root>


output xml:

<root>

      <address>Address</address>
</root>

But i want the output to be:

<root>
      <address>Address</address>
</root>


When i remove the element with xmlmodifier it is creating an empty
space(new line) for the removed element.

Is there any possibility to remove that vtdxml?

Thanks & Regards,
G . Suresh Naidu

[Vtd-xml-users] [ANN] VTD-XML 2.12

[<jz...@xi...>]

VTD-XML 2.12 is released. It has many update to date bug fixes, new
features, and many other improvements. To download, go to 

HTTPS://SOURCEFORGE.NET/PROJECTS/VTD-XML/FILES/VTD-XML/XIMPLEWARE_2.12/
[1]

Links:
------
[1]
http://sitemail.hostway.com/HTTPS://SOURCEFORGE.NET/PROJECTS/VTD-XML/FILES/VTD-XML/XIMPLEWARE_2.12/

Re: [Vtd-xml-users] slow xpath queries

[<jz...@xi...>]

I don't understand scala did you put selectXPath in a loop?  

----- Original Message -----
From: PETER C MEHLITZ 
To:
Cc:
Sent:Thu, 22 Oct 2015 13:55:36 -0700
Subject:[Vtd-xml-users] slow xpath queries

 I have an application using xpath queries that runs about 1/3 slower
than a scala-xml based implementation, which is very surprising to say
the least.

 The program extracts a relatively small amount of data (

Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://sitemail.hostway.com/http:
[3] http://sitemail.hostwaycom/http:
[4] http://ap.evalXPath
[5] http://sitemail.hostway.com/http:
[6] http://ap.evalXPathToString
[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] mailto:Vtd...@li...
[12] https://lists.sourceforge.net/lists/listinfo/vtd-xml-users

[Vtd-xml-users] slow xpath queries

[PETER C M. <pcm...@gm...>]

I have an application using xpath queries that runs about 1/3 slower than a scala-xml based implementation, which is very surprising to say the least.

The program extracts a relatively small amount of data (<10 text/attribute values) out of messages of about 3k size and moderate nesting/complexity (<6 levels, <35 elements), but at a fairly high message rate (anything from 10 -100 msg/sec). Preliminary profiling (sampling) shows the time is spent in constructing the xpath queries (90% in com.ximpleware.xpath.CUP$parser$actions.CUP$parser$do_action).

Test parser structure is as follows (Scala, but there is no scala-ism in there, it directly maps to Java):

  object FPosVTD extends App {
    val gen = new VTDGen
    val ap = new AutoPilot
    ap.declareXPathNameSpace("ns5", ...)
    ...
    time (10000) {
      parse(bytes)  // <<<< the timed code
    }

    @inline final def select (ap: AutoPilot, xpathExpr: String): Int = {
      ap.selectXPath(xpathExpr)
      ap.evalXPath
    }
    @inline final def getString (ap: AutoPilot, xpathExpr: String): String = {
      ap.selectXPath(xpathExpr)
      ap.evalXPathToString
    }

    def parse (b: Array[Byte]): Option[FlightPos] = {
      gen.setDoc_BR(b)
      gen.parse(true)
      ap.bind(gen.getNav)
   
      select(ap,"/ns5:NasFlight")
      val cs = getString(ap, "flightIdentification/@aircraftIdentification")
      ...
      select(ap,"enRoute/position")
      val date = getString(ap, "@positionTime")
      ...

Three questions:

(1) am I doing something stupid here that slows things down?

(2) is there a way to store compiled xpath queries (i.e. the result of AutoPilot.selectXPath(), which seems to be the culprit)? 
BTW - if I use absolute xpath exprs (e.g. "/ns5:NasFlight/flightIdentification/@aircraftIdentification") and skip the select() calls, it gets about 10% slower, which seems to support my hypothesis

(3) is there a way to transmit the VTDs (index data) as a serializable object, together with the message text? 
That would of course factor into overall performance with different (network) clients

Thanks,
-- Peter

Re: [Vtd-xml-users] Help with trimming white space around removed element

[<jz...@xi...>]

I don't see why you need to have trimWhiteSpace call in there.... what
is the goal? 

----- Original Message -----
From: W K 
To:"Vtd...@li..." , "jz...@xi..." 
Cc:
Sent:Mon, 28 Sep 2015 16:11:04 -0400
Subject:Help with trimming white space around removed element

 Can anyone give me a snippet of code that will remove the white space
around an element when that element is removed?  I am struggling to
make VTDNav.expandWhiteSpace() [1] and VTDNav.trimWhiteSpace() [2]
work.  I just need assistance with removing the white space ...
assume that I have already identified the element to remove and I am
removing it with the following code:

xm.remove( [3] vn.trimWhiteSpaces( [4] vn.expandWhiteSpaces( [5]
vn.getElementFragment() [6] ) ) );

I am using a custom version of VTD-XML ... v2.11 with the updated
VTDNav and XMLModifier versions from CVS ... which contains the
expandWhiteSpaces() and trimWhiteSpaces() methods.

Here is a sample XML ... I need to remove the empty element without
the 'activityTitle' attribute:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
  This is what I am ending up with:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
This is what I want to end up with:
  
  
    
    
    
    
  
  
    
    
    
    
  

Thank you for any assistance.
  

Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://sitemail.hostway.com/http:
[3] http://sitemail.hostwaycom/http:
[4] http://sitemail.hostway.com/http:
[5] http://sitemailhostway.com/http:
[6] http://sitemail.hostway.com/http:

Re: [Vtd-xml-users] Help with trimming white space around removed element

[<jz...@xi...>]

btw, would you categorize it as  a serious issue or a nuisance?

----- Original Message -----
From: W K 
To:"Vtd...@li..." , "jz...@xi..." 
Cc:
Sent:Mon, 28 Sep 2015 16:11:04 -0400
Subject:Help with trimming white space around removed element

 Can anyone give me a snippet of code that will remove the white space
around an element when that element is removed?  I am struggling to
make VTDNav.expandWhiteSpace() [1] and VTDNav.trimWhiteSpace() [2]
work.  I just need assistance with removing the white space ...
assume that I have already identified the element to remove and I am
removing it with the following code:

xm.remove( [3] vntrimWhiteSpaces( [4] vn.expandWhiteSpaces( [5]
vn.getElementFragment() [6] ) ) );

I am using a custom version of VTD-XML ... v2.11 with the updated
VTDNav and XMLModifier versions from CVS ... which contains the
expandWhiteSpaces() and trimWhiteSpaces() methods.

Here is a sample XML ... I need to remove the empty element without
the 'activityTitle' attribute:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
  This is what I am ending up with:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
This is what I want to end up with:
  
  
    
    
    
    
  
  
    
    
    
    
  

Thank you for any assistance.
  

Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://sitemail.hostway.com/http:
[3] http://sitemail.hostway.com/http:
[4] http://sitemail.hostway.com/http:
[5] http://sitemail.hostway.com/http:
[6] http://sitemail.hostway.com/http:

Re: [Vtd-xml-users] Help with trimming white space around removed element

[<jz...@xi...>]

 
Looking into it. will get back sooon

----- Original Message -----
From: W K 
To:"Vtd...@li..." , "jz...@xi..." 
Cc:
Sent:Mon, 28 Sep 2015 16:11:04 -0400
Subject:Help with trimming white space around removed element

 Can anyone give me a snippet of code that will remove the white space
around an element when that element is removed?  I am struggling to
make VTDNav.expandWhiteSpace() [1] and VTDNav.trimWhiteSpace() [2]
work.  I just need assistance with removing the white space ...
assume that I have already identified the element to remove and I am
removing it with the following code:

xm.remove( [3] vn.trimWhiteSpaces( [4] vn.expandWhiteSpaces( [5]
vn.getElementFragment() [6] ) ) );

I am using a custom version of VTD-XML ... v2.11 with the updated
VTDNav and XMLModifier versions from CVS ... which contains the
expandWhiteSpaces() and trimWhiteSpaces() methods.

Here is a sample XML ... I need to remove the empty element without
the 'activityTitle' attribute:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
  This is what I am ending up with:

  
    
    
    
    
    
  
  
    
    
    
    
    
  
  
This is what I want to end up with:
  
  
    
    
    
    
  
  
    
    
    
    
  

Thank you for any assistance.
  

Links:
------
[1] http://sitemail.hostway.com/http:
[2] http://sitemail.hostway.com/http:
[3] http://sitemail.hostway.com/http:
[4] http://sitemail.hostway.com/http:
[5] http://sitemail.hostway.com/http:
[6] http://sitemail.hostway.com/http:

[Vtd-xml-users] Help with trimming white space around removed element

[W K <wka...@ho...>]

Can anyone give me a snippet of code that will remove the white space around an element when that element is removed?  I am struggling to make VTDNav.expandWhiteSpace() and VTDNav.trimWhiteSpace() work.  I just need assistance with removing the white space ... assume that I have already identified the element to remove and I am removing it with the following code:

xm.remove( vn.trimWhiteSpaces( vn.expandWhiteSpaces( vn.getElementFragment() ) ) );

I am using a custom version of VTD-XML ... v2.11 with the updated VTDNav and XMLModifier versions from CVS ... which contains the expandWhiteSpaces() and trimWhiteSpaces() methods.

Here is a sample XML ... I need to remove the empty element without the 'activityTitle' attribute:

  <BudgetSummary>
    <SummaryLineItem activityTitle="N/A"/>
    <SummaryLineItem activityTitle=""/>
    <SummaryLineItem activityTitle="SummaryLineItem Title 1"/>
    <SummaryLineItem activityTitle=""/>
    <SummaryTotals/>
  </BudgetSummary>
  <BudgetCategories>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="N/A"/>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="CategorySet Title 1"/>
    <CategoryTotals/>
  </BudgetCategories>
  
  This is what I am ending up with:

  <BudgetSummary>
    <SummaryLineItem activityTitle="N/A"/>
    <SummaryLineItem activityTitle=""/>
    <SummaryLineItem activityTitle="SummaryLineItem Title 1"/>
    <SummaryLineItem activityTitle=""/>
    
  </BudgetSummary>
  <BudgetCategories>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="N/A"/>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="CategorySet Title 1"/>
    
  </BudgetCategories>
  
This is what I want to end up with:
  
  <BudgetSummary>
    <SummaryLineItem activityTitle="N/A"/>
    <SummaryLineItem activityTitle=""/>
    <SummaryLineItem activityTitle="SummaryLineItem Title 1"/>
    <SummaryLineItem activityTitle=""/>
  </BudgetSummary>
  <BudgetCategories>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="N/A"/>
    <CategorySet activityTitle=""/>
    <CategorySet activityTitle="CategorySet Title 1"/>
  </BudgetCategories>


Thank you for any assistance.

 		 	   		  

Re: [Vtd-xml-users] Publication of 2.12 to maven central?

[<jz...@xi...>]

It is active... version 2.12 is on the way.... I promise it will
come 

----- Original Message -----
From: 
To:
Cc:
Sent:Fri, 7 Aug 2015 15:40:16 -0400
Subject:[Vtd-xml-users] Publication of 2.12 to maven central?

Hello,
I am doing an evaluation of XML parsers for the next project at my
company and I'm convinced that VTD-XML is the right solution.  Very
nice work!
However, I have hit the NodeRecorder bug that is in vtd-xml 2.11 (Java
library) that is documented here:
http://stackoverflow.com/questions/14987792/unexpected-noderecorder-behaviour
[1]
I understand that the latest code in CVS fixes this, but it would be
more palatable to my company if the 2.12 version had been officially
cut and released to maven central, rather than having to pull source
from CVS.
I hope that VTD-XML remains active and can get this next release out
soon.  Do you have plans to do that?
-Michael Peterson
 

Links:
------
[1]
http://stackoverflow.com/questions/14987792/unexpected-noderecorder-behaviour

Re: [Vtd-xml-users] Publication of 2.12 to maven central?

[<mpe...@gm...>]

Meanwhile, I downloaded the latest source code from sourceforge, but I
can't see how to build it.  I downloaded the tarball and the ximple-dev
module from CVS, but I don't see any build files, such as build.xml,
pom.xml, gradle.build or a even makefile for the Java system.  (I see
makefiles for the c/c++ versions only.)

How does one build the Java VTD-XML library from source?

-Michael

On Fri, Aug 7, 2015 at 3:40 PM, <mpe...@gm...> wrote:

> Hello,
>
> I am doing an evaluation of XML parsers for the next project at my company
> and I'm convinced that VTD-XML is the right solution.  Very nice work!
>
> However, I have hit the NodeRecorder bug that is in vtd-xml 2.11 (Java
> library) that is documented here:
> http://stackoverflow.com/questions/14987792/unexpected-noderecorder-behaviour
>
> I understand that the latest code in CVS fixes this, but it would be more
> palatable to my company if the 2.12 version had been officially cut and
> released to maven central, rather than having to pull source from CVS.
>
> I hope that VTD-XML remains active and can get this next release out
> soon.  Do you have plans to do that?
>
> -Michael Peterson
>
>

[Vtd-xml-users] Publication of 2.12 to maven central?

[<mpe...@gm...>]

Hello,

I am doing an evaluation of XML parsers for the next project at my company
and I'm convinced that VTD-XML is the right solution.  Very nice work!

However, I have hit the NodeRecorder bug that is in vtd-xml 2.11 (Java
library) that is documented here:
http://stackoverflow.com/questions/14987792/unexpected-noderecorder-behaviour

I understand that the latest code in CVS fixes this, but it would be more
palatable to my company if the 2.12 version had been officially cut and
released to maven central, rather than having to pull source from CVS.

I hope that VTD-XML remains active and can get this next release out soon.
Do you have plans to do that?

-Michael Peterson

[Vtd-xml-users] Was schema validating ever implemented in VTD-XML?

[<mpe...@gm...>]

Hi,

I've been lurking on the group for a while waiting for a time when I would
need to use VTD-XML and the time has finally come.  I see that some slides
and documents on the web from ~2012 and before indicated that having
VTD-XML be a validating parser (against XSD) was a planned feature.

But I've not found any documentation about whether that's been completed.
Can you give me an update?  It has been implemented, could you provide a
link to documentation on how to use it?

Thanks,
Michael

[Vtd-xml-users] Getting element attributes using AutoPilot.selectAttr()

[W K <wka...@ho...>]

Has anyone gotten this to work properly?

I came across this post:

https://ximpleware.wordpress.com/2011/01/10/how-to-read-all-attributes-of-an-element-in-vtd-xml/

I
 remember needing to get all attributes from an element a few years ago 
and tried using AutoPilot ... as it mentioned in the post ... however, I
 could not get it to work.

I have a work-around, but I want to 
use the AutoPilot.selectAttr() method because it is exactly what I 
need.  Below is the sample code and xml file ... it uses IOUtils from
 apache commons just to load the file.

I even re-compiled v2.11 
with the latest AutoPilot and VTDNav (I just dropped those two files 
into the v.2.11 code base) and it still does not return all of the 
attributes ... it just returns the element name with the ns prefix.  
Well, if you run the class below, you will see the result.  I specifically 
need the xmlns declarations/attributes.  I even have the AutoPilot load 
all of the ns prefix declarations before trying to get the attributes.

Thanks for your help.

The XML:

<RR_SF424_2_0:RR_SF424_2_0 
    xmlns:RR_SF424_2_0="http://apply.grants.gov/forms/RR_SF424_2_0-V2.0" 
    xmlns:att="http://apply.grants.gov/system/Attachments-V1.0"
    xmlns:glob="http://apply.grants.gov/system/Global-V1.0" 
    xmlns:globLib="http://apply.grants.gov/system/GlobalLibrary-V2.0"
    RR_SF424_2_0:FormVersion="2.0" />


The sample code:

import java.util.HashMap;
import java.util.Map;
import java.util.Set;

import org.apache.commons.io.IOUtils;
import org.apache.commons.lang.StringUtils;

import com.ximpleware.AutoPilot;
import com.ximpleware.VTDGen;
import com.ximpleware.VTDNav;

public class VtdXmlObj {
    
    public static final String XMLNS_ATTR = "xmlns";
    public static final String XMLNS_PREFIX = XMLNS_ATTR + ":";
    
    private VTDNav vn;
    
    private AutoPilot ap = new AutoPilot();
    
    private boolean namespacesAdded = false;
    
    
    /* Constructor(s) */
    
    public VtdXmlObj( byte[] xmlBytes ) throws Exception {
        init( xmlBytes );
    }
    
    /* Public Method(s) */
    
    public Map<String, String> getXmlNsMapForCurrentElement() {
        Map<String, String> xmlNsMap = new HashMap<String, String>();
        
        try {
            String attrName = null;
            String nsPrefix = null;
            String nsUrl = null;
            String mapNsUrl = null;
            
            ap.selectAttr( "*" );
//            ap.selectXPath( "@*" );
            int i = -1;
            
            while( ( i = ap.iterateAttr() ) != -1 ) {
                System.out.println( "index: " + i );
                attrName = vn.toNormalizedString( vn.getCurrentIndex() );
                System.out.println( "attr name: " + attrName );
                
                if ( attrName.startsWith( XMLNS_ATTR ) ) {
                    nsPrefix = attrName.substring( attrName.indexOf( ":" ) + 1 );
                    nsUrl = vn.toNormalizedString( vn.getCurrentIndex() + 1 );
                    
                    mapNsUrl = xmlNsMap.get( nsPrefix );
                    if ( StringUtils.isBlank( mapNsUrl ) ) {
                        System.out.println( "add ns: " + nsPrefix + "=" + nsUrl );
                        xmlNsMap.put( nsPrefix, nsUrl );
                    } else {
                        if ( !mapNsUrl.equals( nsUrl ) ) {
                            System.out.println( nsPrefix + " [" + mapNsUrl + "] --- [" + nsUrl + "]" );
                        }// if
                        
                    }// if-else
                    
                }// if
                
            }// for
            
        } catch ( Exception e ) {
            System.out.println( "Cannot add all namespaces: " + e.getMessage() );
        }// try-catch
        
        return xmlNsMap;
        
    }// getXmlNsMapForCurrentElement
    
    
    /* Private Method(s) */
    
    private void init( byte[] xmlBytes ) throws Exception {
        try {
            
            if ( xmlBytes == null || xmlBytes.length == 0 ) {
                throw new Exception( "XML bytes are blank" );
            }// if
            
            System.out.println( "xml size: " + xmlBytes.length );
            VTDGen vGen = new VTDGen();
            vGen.setDoc( xmlBytes );
            vGen.parse( true );//set namespace awareness
            vn = vGen.getNav();
            System.out.println( "loaded xml successfully" );
            
            addAllNamespaces( ap );
            ap.bind( vn );
            
        } catch ( Exception e ) {
            System.out.println( "Exception parsing xml bytes: " + e.getMessage() );
            throw new Exception( e.getMessage() );
        }// try-catch
        
    }// init
    
    
    public void addAllNamespaces( AutoPilot ap ) {
        try {
            if ( namespacesAdded ) {
                System.out.println( "namespaces already added" );
                return;
            }// if
            
            int size = vn.getTokenCount();
            Map<String, String> nsMap = getXmlNsMap();
            System.out.println( "unique xml ns count: " + nsMap.size() );
            
            nsMap.putAll( XMLConstants.getCommonXmlNsMap() );
            System.out.println( "updated nsMap size: " + nsMap.size() );
            
            int count = 0;
            Set<String> nsPrefixes = nsMap.keySet();
            for ( String prefix : nsPrefixes ) {
                count++;
                System.out.println( "adding namespace: " + prefix + "=" + nsMap.get( prefix ) );
                ap.declareXPathNameSpace( prefix, nsMap.get( prefix ) );
            }// for
            
            System.out.println( "ns added count: " + count );
            
            namespacesAdded = true;
            
        } catch ( Exception e ) {
            System.out.println( "Cannot add all namespaces: " + e.getMessage() );
        }// try-catch
    }// addAllNamespaces
    
    
    public Map<String, String> getXmlNsMap() {
        Map<String, String> xmlNsMap = new HashMap<String, String>();
        try {
            int size = vn.getTokenCount();
            String nsPrefix = null;
            String nsUrl = null;
            
            String mapNsUrl = null;
            
            for ( int i= 0; i < size; i++ ) {
                String token = vn.toNormalizedString2( i );
                
//                if ( token.startsWith( "xmlns:" ) ) {
                if ( vn.startsWith( i, XMLNS_PREFIX ) ) {
                    nsPrefix = token.substring( token.indexOf( ":" ) + 1 );
                    nsUrl = vn.toNormalizedString2( i + 1 );
                    
                    mapNsUrl = xmlNsMap.get( nsPrefix );
                    if ( StringUtils.isBlank( mapNsUrl ) ) {
                        System.out.println( "add ns: " + nsPrefix + "=" + nsUrl );
                        xmlNsMap.put( nsPrefix, nsUrl );
                    } else {
                        if ( !mapNsUrl.equals( nsUrl ) ) {
//                            System.out.println( nsPrefix + " [" + mapNsUrl + "] --- [" + nsUrl + "]" );
                        }// if
                    }// if-else
                }// if
            }// for
            
        } catch ( Exception e ) {
            System.out.println( "Cannot add all namespaces: " + e.getMessage() );
        }// try-catch
        
        return xmlNsMap;
        
    }// getXmlNsMap
    
    
    /* ==================== */
    
    public static void main( String[] args ) {
        
        String fileName = null;
        fileName = "single-empty-element.xml";
        
        try {
            byte[] xmlBytes = IOUtils.toByteArray( VtdXmlObj.class.getResourceAsStream( fileName ) );
            System.out.println( "xml bytes: " + xmlBytes.length );
            
            VtdXmlObj xmlObj = new VtdXmlObj( xmlBytes );
            xmlObj.getXmlNsMapForCurrentElement();
            
        } catch ( Exception e ) {
            System.out.println( "Exception: " + e.getMessage() );
        }// try-catch
        
    }// main
    
}
 		 	   		  

Re: [Vtd-xml-users] where can I find the actual vtdNav.java?

[<jz...@xi...>]

Try
thishttp://vtd-xml.cvs.sourceforge.net/viewvc/vtd-xml/ximple-dev/com/ximpleware/VTDNav.java?view=log 

----- Original Message -----
From: "Jaekel Birgit" 
To:"vtd...@li..." 
Cc:
Sent:Tue, 16 Jun 2015 10:31:19 +0000
Subject:[Vtd-xml-users] where can I find the actual vtdNav.java?

	Hi!

	I’m new here and I am using VTD-XML in a rail project. We build a
java project where we use the sources which I got from
http://sourceforge.net/projects/vtd-xml/files/vtd-xml/ximpleware_2.11/
[1]. The reading of the railml data works quite well (thank you for
your work on this), but now I tried to set namespace awareness to
false for parsing. This does not seem to work.

	I’ve read (here
http://sourceforge.net/p/vtd-xml/discussion/379067/thread/16d902de/#2d5f
[2]) that there might me the possibility to use a VTDNav.java [3]
where this bus (http://sourceforge.net/p/vtd-xml/bugs/32/ [4]) is
fixed, but I’m not able to find this file on CVS.

	  

	Could you please provide me a link or send the file? This would be a
great help.

	  

	Thank you and best regards,

	Birgit Jaekel

	  

Links:
------
[1]
http://sourceforge.net/projects/vtd-xml/files/vtd-xml/ximpleware_2.11/
[2]
http://sourceforge.net/p/vtd-xml/discussion/379067/thread/16d902de/#2d5f
[3] http://VTDNav.java
[4] http://sourceforge.net/p/vtd-xml/bugs/32/

[Vtd-xml-users] where can I find the actual vtdNav.java?

[Jaekel, B. <bir...@tu...>]

Hi!
I'm new here and I am using VTD-XML in a rail project. We build a java project where we use the sources which I got from http://sourceforge.net/projects/vtd-xml/files/vtd-xml/ximpleware_2.11/. The reading of the railml data works quite well (thank you for your work on this), but now I tried to set namespace awareness to false for parsing. This does not seem to work.
I've read (here http://sourceforge.net/p/vtd-xml/discussion/379067/thread/16d902de/#2d5f) that there might me the possibility to use a VTDNav.java where this bus (http://sourceforge.net/p/vtd-xml/bugs/32/) is fixed, but I'm not able to find this file on CVS.

Could you please provide me a link or send the file? This would be a great help.

Thank you and best regards,
Birgit Jaekel