Breakpoint in include file!?
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 1
- Joined: Fri Dec 19, 2014 6:12 pm
Breakpoint in include file!?
Post by ruperthawkes »
Hi,
I am using XML Developer 16.1 and setting a breakpoint in an include XLST file. But the debugger doesn't stop at the breakpoint.
Any ideas? Ta.
I am using XML Developer 16.1 and setting a breakpoint in an include XLST file. But the debugger doesn't stop at the breakpoint.
Any ideas? Ta.
-
- Posts: 846
- Joined: Mon Dec 05, 2011 6:04 pm
Re: Breakpoint in include file!?
Hello,
Please note that the breakpoints you set in the debugger are in direct relation with the processor you are using (by default, that is Saxon). Given this, you should make sure that you are setting the breakpoints in valid locations. If a breakpoint is set in a location where Saxon is not supposed to stop, then the respective breakpoint will be ignored.
For instance, if you have some breakpoints set on empty or commented lines or the lines are not reached by the processor, then the debugger won't stop at them.
Besides this, there are also optimizations performed by the Saxon engine of the source code and the breakpoints which were set on optimized locations are not considered.
For Saxon-EE/PE/HE this can be resolved by decreasing the optimization level to 0. This can be adjusted in Options -> Preferences -> XML -> XSLT-FO-XQuery -> XSLT -> Saxon -> Saxon-HE/PE/EE (the "optimization level" option).
Regards,
Costin
Please note that the breakpoints you set in the debugger are in direct relation with the processor you are using (by default, that is Saxon). Given this, you should make sure that you are setting the breakpoints in valid locations. If a breakpoint is set in a location where Saxon is not supposed to stop, then the respective breakpoint will be ignored.
For instance, if you have some breakpoints set on empty or commented lines or the lines are not reached by the processor, then the debugger won't stop at them.
Besides this, there are also optimizations performed by the Saxon engine of the source code and the breakpoints which were set on optimized locations are not considered.
For Saxon-EE/PE/HE this can be resolved by decreasing the optimization level to 0. This can be adjusted in Options -> Preferences -> XML -> XSLT-FO-XQuery -> XSLT -> Saxon -> Saxon-HE/PE/EE (the "optimization level" option).
Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
oXygen XML Editor and Author Support
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ 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