Error location is not displayed
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 5
- Joined: Fri Jun 11, 2004 11:18 am
- Location: Belgium - Brussels
- Contact:
Error location is not displayed
hello,
Great surprise today with the release 4.1.
But I already can announce a little bug.
The location of an error is not displayed. It's a little bit annoying when I debug.
Also, I notice the fonctionnality Xwatch don't seem functional in the version 4.0 and now 4.1. I work on windows plateform and I have the J2re1.4.2_04.
regards,
Aurélien Van Hamme
Great surprise today with the release 4.1.
But I already can announce a little bug.
The location of an error is not displayed. It's a little bit annoying when I debug.
Also, I notice the fonctionnality Xwatch don't seem functional in the version 4.0 and now 4.1. I work on windows plateform and I have the J2re1.4.2_04.
regards,
Aurélien Van Hamme
Post by stefan »
Usually, the error location is shown. It will be helpfull if you can send a document sample at support@oxygenxml.com for a detailed look.
Xwatch evaluates XPath expressions during debugging. What XPath expressions did you try ?
Xwatch evaluates XPath expressions during debugging. What XPath expressions did you try ?
-
- Posts: 5
- Joined: Fri Jun 11, 2004 11:18 am
- Location: Belgium - Brussels
- Contact:
Well for the XWatch(XPath):
I transform a xml docbook with the docbook stylesheet. And when I debug step by step, I don't see anything in the Xwatch during all the transformation.
For the error location, I just do another test with the basic stylesheet:
When the debugger parse this file, it find a error because it doesn't found the end-tag for the variable.
With the version 4.0, it shows the error location at line 6.3 but with the version 4.1, the error location is empty.
Aur
I transform a xml docbook with the docbook stylesheet. And when I debug step by step, I don't see anything in the Xwatch during all the transformation.
For the error location, I just do another test with the basic stylesheet:
Code: Select all
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<xsl:variable name="topic">Hello world
</xsl:template>
</xsl:stylesheet>
With the version 4.0, it shows the error location at line 6.3 but with the version 4.1, the error location is empty.
Aur
-
- Posts: 5
- Joined: Fri Jun 11, 2004 11:18 am
- Location: Belgium - Brussels
- Contact:
Other example:
Same case, if I use this stylesheet:
The error description is :
I notice also a strange behavior. For the moment, all test I made was with the Saxon 5.5.3 parser. I made one test with the Xalan Java 2.5.1 and here he shows me the error location for the end-tag error (described in my previous post) but no error location for the $topice error (described in this post).
regards,
Aur
Same case, if I use this stylesheet:
Code: Select all
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<xsl:variable name="topic">Hello world</xsl:variable>
<xsl:value-of select="$topice"/>
</xsl:template>
</xsl:stylesheet>
but no error location.F The element type "xsl:variable" must be terminated by the matching end-tag "</xsl:variable>".
I notice also a strange behavior. For the moment, all test I made was with the Saxon 5.5.3 parser. I made one test with the Xalan Java 2.5.1 and here he shows me the error location for the end-tag error (described in my previous post) but no error location for the $topice error (described in this post).
regards,
Aur
Post by stefan »
The Results Panel/ Location shows details only if both line and column information is provided by the parser. If only line info is known for that error, the Location field is empty.
This happens usually with Saxon parser, but you can still click on the error in order to get that line highlighted into editor.
I agree that a better choice will be to show something like "line:-1".
This happens usually with Saxon parser, but you can still click on the error in order to get that line highlighted into editor.
I agree that a better choice will be to show something like "line:-1".
-
- Posts: 5
- Joined: Fri Jun 11, 2004 11:18 am
- Location: Belgium - Brussels
- Contact:
hello, thanks for the answer.
So, is it a change realised for the new release (4.1)? If yes, I find it less practical.
In the previous version, the debugger shows all my error locations. This locations had the form 21:1, 45:1, 68:1.
Henceforth, I will click on the error.
Any idea for the Xwatch problem?
So, is it a change realised for the new release (4.1)? If yes, I find it less practical.
In the previous version, the debugger shows all my error locations. This locations had the form 21:1, 45:1, 68:1.
Henceforth, I will click on the error.

Any idea for the Xwatch problem?
Post by stefan »
I did a test with the following:
source: <oxygen_install_dir>\samples\docbook\sample.xml
style: <oxygen_install_dir>\docbook\xsl\html\docbook.xsl
where in my case <oxygen_install_dir> is C:\Program Files\Oxygen4.1
I set the following XWatch expression:
name() - name of the source node.
Usually during a Docbook debugging the source content is not changing at every step (it could take some number of steps to see the source context changed) but when this happen you can see the name() changing.
How did you test the XWatch functionality ?
source: <oxygen_install_dir>\samples\docbook\sample.xml
style: <oxygen_install_dir>\docbook\xsl\html\docbook.xsl
where in my case <oxygen_install_dir> is C:\Program Files\Oxygen4.1
I set the following XWatch expression:
name() - name of the source node.
Usually during a Docbook debugging the source content is not changing at every step (it could take some number of steps to see the source context changed) but when this happen you can see the name() changing.
How did you test the XWatch functionality ?
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