XSLT debugging problem in Oxygen 9 for Eclipse
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 3
- Joined: Thu Nov 29, 2007 9:24 pm
XSLT debugging problem in Oxygen 9 for Eclipse
When I set breakpoints in either an XSLT or XML file, the breakpoints don't show up in the Breakpoints view. If I run a debug session, the debugger never stops at any of the breakpoints. An example of where I've set a breakpoint is
<xsl:template match="node() | @*"> // breakpoint set on this line
<xsl:copy>
<xsl:apply-templates select="@*|node()" />
</xsl:copy>
</xsl:template>
For this input XML
// snip //
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Example Glossary</title>
<link href="./css/commonltr.css" type="text/css" rel="stylesheet"></link>
<link href="./css/glossary.css" type="text/css" rel="stylesheet"></link>
</head>
<body>
<h1 class="topictitle1">Example Glossary</h1>
<div>
......
// snip //
I've uninstalled and reinstalled Oxygen but that hasn't seemed to help. Any ideas?
<xsl:template match="node() | @*"> // breakpoint set on this line
<xsl:copy>
<xsl:apply-templates select="@*|node()" />
</xsl:copy>
</xsl:template>
For this input XML
// snip //
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Example Glossary</title>
<link href="./css/commonltr.css" type="text/css" rel="stylesheet"></link>
<link href="./css/glossary.css" type="text/css" rel="stylesheet"></link>
</head>
<body>
<h1 class="topictitle1">Example Glossary</h1>
<div>
......
// snip //
I've uninstalled and reinstalled Oxygen but that hasn't seemed to help. Any ideas?
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
Hello,
I cannot reproduce the problem. The debugger always stops at the breakpoint set on the line <xsl:template match="node() | @*"> when the transformation matches this template. Does Eclipse log errors to the Error Log view or to the Problems view? What is your Eclipse build number displayed in the Help -> About Eclipse dialog and your oXygen plugin build number displayed in Window -> Preferences -> oXygen? Can you send us sample files for reproducing the problem?
Regards,
Sorin
I cannot reproduce the problem. The debugger always stops at the breakpoint set on the line <xsl:template match="node() | @*"> when the transformation matches this template. Does Eclipse log errors to the Error Log view or to the Problems view? What is your Eclipse build number displayed in the Help -> About Eclipse dialog and your oXygen plugin build number displayed in Window -> Preferences -> oXygen? Can you send us sample files for reproducing the problem?
Regards,
Sorin
-
- Posts: 3
- Joined: Thu Nov 29, 2007 9:24 pm
The only error I see is "Premature end of file" but the Resource and Line fields are blank. There are no Problems listed.
Here's my environment:
Eclipse Build id: I20070625-1500
Oxygen Build: 2007112709
I've sent a bug report to tech support with copies of the following files.
Here's the XSL:
Here's the XML
Here's my environment:
Eclipse Build id: I20070625-1500
Oxygen Build: 2007112709
I've sent a bug report to tech support with copies of the following files.
Here's the XSL:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsltu="http://xsltunit.org/0/"
version="1.0">
<xsl:output omit-xml-declaration="yes"/>
<xsl:template match="//xsltu:assert[@outcome = 'failed']"> //BREAKPOINT
<failures/>
</xsl:template>
</xsl:stylesheet>
Code: Select all
<xsltu:tests xmlns:xsltu="http://xsltunit.org/0/" xmlns:xalan="http://xml.apache.org/xslt">
<xsltu:test id="test-sorting">
<xsltu:assert id="first-term-is-aaterm" outcome="passed"/> // BREAKPOINT
<xsltu:assert id="last-term-is-zterm" outcome="passed"/>
<xsltu:assert id="hterm-does-not-exist" outcome="passed"/>
</xsltu:test>
<xsltu:test id="test-grouping">
<xsltu:assert id="a-term-node-count-is-2" outcome="passed"/>
<xsltu:assert id="group-count-is-8" outcome="passed"/>
</xsltu:test>
<xsltu:test id="test-alpha-navigation">
<xsltu:assert id="nav-letter-count-is-8" outcome="failed"/> //BREAKPOINT
<xsltu:assert id="nav-link-count-is-8" outcome="passed"/>
<xsltu:assert id="group-anchor-count-is-8" outcome="passed"/>
<xsltu:assert id="alpha-nav-link-elements-correct" outcome="failed"/>
</xsltu:test>
</xsltu:tests>
-
- Posts: 3
- Joined: Thu Nov 29, 2007 9:24 pm
I just realized what is going on. In the Oxygen debugging perspective I was setting breakpoints by right clicking in the left-hand gutter of the XML files which produces a green breakpoint icon. I just discovered that if I right click in the XML file I have an "Add Breakpoint" option. Using that sets a red breakpoint icon in the gutter. After setting the breakpoint this way I notice that the breakpoint is listed in the Breakpoints view. So, I must have been setting a breakpoint for a different language.
Also noted: the oxygen documentation states
In any case, I'm able to debug XSLT now. Thanks.
Also noted: the oxygen documentation states
There is no Breakpoints menu item in my Edit menu. However, left-clicking in the gutter produces a red breakpoint icon. I also noticed that there are two "Add Breakpoint" menu items in the right click context menu, the second (bottom) one being the one for Oxygen. I think the green breakpoint icons are for the PyDev plugin that I also have installed but haven't used in a while. This is a little confusing and might be clarified if both the Oxygen and PyDev plugins labeled the type of breakpoint to be added.Select Edit → Breakpoints → Create or directly click with the mouse the left side stripe of the editor window on the line where you want the breakpoint to be.
In any case, I'm able to debug XSLT now. Thanks.
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
The Edit -> Breakpoints menu is available only in oXygen standalone. We will update the Eclipse plugin documentation.esroberts wrote:Also noted: the oxygen documentation states
There is no Breakpoints menu item in my Edit menu.Select Edit → Breakpoints → Create or directly click with the mouse the left side stripe of the editor window on the line where you want the breakpoint to be.
The icon of the breakpoint (a red bullet for oXygen plugin) and the presence in the Breakpoints view of the oXygen XSLT Debugger perspective should make the difference. We will consider also changing the name of the menu item.esroberts wrote:This is a little confusing and might be clarified if both the Oxygen and PyDev plugins labeled the type of breakpoint to be added.
Regards,
Sorin
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service