Community
Participate
Working Groups
We either need a seperate view, or better detection on when a variable contains result-Node data or is just a string. If nodeset result, then it should be expandable like the Java variables that are Class variables. Currently all variables display as string results.
Nodes are now dislayed differently to strings, so they are at least distinguishable. The nodeset is not expandable however. I'll leave that as an enhancement.
Mass Migration to wtp.inc.xsl
We should try to make this expandable in the the 1.0 time frame. Currently when debugging with Xalan it displays the node as: org.apache.xml.dtm.ref.DTMNodeProxy@1383209 Which isn't that helpful during debugging scenarios. A work around is to extract a value from the node, and store it in a xsl:variable so that at least part of the text can be reviewed, but this is an added step that doesn't need to exist. Result Set Fragments for XSLT 1.0 should be expandable as well as Node Set.
Doug I can take a look at this one to see if I can enhance this.
Nodes, can be expanded, strings can't. Also, empty Nodesets can not be expanded. Right now, a Nodeset, will return some xml markup representing the values of the nodeset. i.e. <doc> <test>some text</test> </doc> The XSLValue should parse this and build an appropriate DOM document which can be be parsed, and then displayed as necessary when the nodelist is expanded.
Nodesets are now expandable. Need to work on differentiating between Elemens, Attributes, Comments and Processing instructions.
All XML nodes are rendered with a different image according to their type in the list.
This is working pretty well now. I'm sure there are some problems with large markup streams, but will address those as we find them. The functionality requested by this bug is implemented.
mass update to 3.1 target due to movement from wtp incubator to wtp source editing lost the original milestones.
