XML Iter with XPath using node() fails on xml comments

FinalBuilder Bugs
1
I'm using an XML Iterator and if there are XML comments at the same level as the nodes I'm selecting it fails with the following message:
 
Loading XML file J:\my.xml
Evaluating XPath & selecting XML nodes...
Found 17 Nodes
The iterator could not be initialised.
Invalid node type (8), please check your XPath
The value of the node selected is:  blah 

 

Example XPath: /Build/node()

XML Comment: <Build><!-- This is a comment that blo --><GoodNode /></Build>

 

2

Hi Nelson

Paul and I fixed this one late yesterday, the code that generates the xpath to a node was not dealing with comment nodes correctly. This build has the fix :

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1684.exe

3

 Hi Vincent,

I tried 6.3.1684 but the bug is still happening.  Attaching example.

-Nelson

I think a different error though:

Action Messages:
Error updating iterator status after iteration #2 :
Error Setting Variable: Interface not supported
 

002_001_XMLIterCommentBug.zip (23.589 KB)
4

Hi Nelson

This was the same error with a different cause. We were assuming that the nodes selected by xpath would only be elements, but using the node() function also selects comments (not sure if that’s what you intended or not). I spent this afternoon reworking the code that generates the xpath for a given node. The old version was not reliable with some node types (didn’t handle comments or attribute nodes properly and could generate invalid xpath). The new version is I believe much more reliable. I tested with a bunch of different xml documents with and without namspaces and various xpath statements and it seems a lot more robust.

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1706.exe

We are hoping to release an official update tomorrow so please let us know asap if this build is not working as expected. I will continue testing here, however there are an infinite number of xpath/xml combination’s so it’s still possible I’ve missed something.


5

Hi Vincent,

I did not need to actually select the comments. I tested the build and it fixes the comment issue, but the behavior of the iterator has changed a little. Previously the iterator would return a non indexed XPath if there was only node being returned. Now the returned XPath is always indexed. Also I see comment() nodes are being returned now. I don’t think this effects our older scripts, but my new stuff expects different values. I am rewriting it now to support the new build.

One strange effect of upgrading is my tool paths have been changed.

SVN Path went from: C:\Program Files\CollabNet Subversion Client to C:\Program Files\CollabNet Subversion

VVS2005 seems to be have changed to C:\Program Files\Microsoft Visual Studio 9.0 when before it was set to C:\Program Files\Microsoft Visual Studio 8\Common7\IDE.

-Nelson

6

FYI I believe I finished updating my scripts so it appears they now work correctly with the new XML Iterator return values.

7

Also just upgraded another machine and that didn't seem to change the tool paths. Maybe that's a non-issue.

8


Hi There!
  This is Jannsenn!
Im new in this site!
   I hope I can have more friends here and I can ans. anyone for there question or prob..
     The new version is I believe much more reliable. I tested with a bunch of different xml documents with and without namspaces and various xpath statements and it seems a lot more robust.
    Keep on posting Guys!
  Thanks!...
Have a nice Day!.....