[oXygen-user] debugger questions

[Sorin Ristache]

Hello,

Thank you for the feedback.
What is the version of oXygen that you are running? I see no "add break 
point" action in any right click menu in an editor panel or in any view 
of the Debugger perspective.

An older version of oXygen had the problem of not updating the variables 
while running the transformation step by step but it should be fixed in 
the latest version, that is version 8.2. If the problem was not fixed 
for your case can you send us some sample files and specify the line 
where I should stop the transformation and run step by step for 
reproducing it?

XSLT processors stop the transformation only on lines which contain the 
end of an opening tag. Thus oXygen forbids you to place a breakpoint on 
a line where the processing will not stop and to wonder why it did not 
stop while running the transformation. The reason of skipping such 
"breakpoints" is not obvious so it needs to be stated explicitly. So if 
you have a variable definition like

         <xsl:variable name="var">
             <xsl:apply-templates select="a[@att='v1']"/>
         </xsl:variable>

you cannot place a breakpoint on the line

         </xsl:variable>

You have to place it on the line

         <xsl:variable name="var">

For the null value of XPath expressions inside loops please give a 
specific example. We need to check if variable optimizations are applied 
to the XPath expressions used in the stylesheet or the debugger does not 
evaluate the expression correctly. Also specify the XSLT processor set 
in the processor combo of the Debugger perspective.


Regards,
Sorin


James Don wrote:
> Hello,
> 
> Just wanted to send some feed back on the tool regarding the xsl debugger:
> 
> - Why do breakpoints not set ? There are 2 "add break point"s in the 
> right click menu ... only 1 seems to add break points ... the other just 
> changes the colour of the break point.
> 
> - Watched variables don't update as you step in the debugger ... unless 
> of course you click around in the gui to force a refresh ... this makes 
> debugging pretty annoying ...
> 
> - Can't break on variable definitions ... i keep getting an error msg 
> that says "Breakpoints can only be created on a line containing the end 
> of a start tag" ?
> 
> - Inside some looping constructs it seems watches on certain xpaths 
> return null ... even though variables dependent on the same xpath are 
> set ...