Is it possible to Xalan inside the Editor perspective?
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 11
- Joined: Mon Jul 30, 2007 6:19 pm
- Location: Charlotte, NC USA
Is it possible to Xalan inside the Editor perspective?
I can switch between Saxon and Xalan in debug perspective but not in the Editor perspective.
In the Editor perspective I am given the combo box options MSXML.NET AND MSXML.40 - which is strange - because when I run I get the following Saxon error:
SystemID: C:\Projects\GPS-POCS\p2p.poc\xslt\test.xsl
Location: 45:0
E[Saxon6.5.5] The URI http://exslt.org/strings does not identify an external Java class
In debug perspective I can switch to Xalan and it runs fine. How do I do that in Editor perspective?
Thanks,
Radu.
In the Editor perspective I am given the combo box options MSXML.NET AND MSXML.40 - which is strange - because when I run I get the following Saxon error:
SystemID: C:\Projects\GPS-POCS\p2p.poc\xslt\test.xsl
Location: 45:0
E[Saxon6.5.5] The URI http://exslt.org/strings does not identify an external Java class
In debug perspective I can switch to Xalan and it runs fine. How do I do that in Editor perspective?
Thanks,
Radu.
-
- Posts: 11
- Joined: Mon Jul 30, 2007 6:19 pm
- Location: Charlotte, NC USA
Re: Is it possible to Xalan inside the Editor perspective?
Never mind - one has to configure it in the transformation scenario - Transformer combo box - select Xalan.
Still it would have been nice to see what engine am I running in the Editor perspective.
Thanks,
Radu.
Still it would have been nice to see what engine am I running in the Editor perspective.
Thanks,
Radu.
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Re: Is it possible to Xalan inside the Editor perspective?
Post by sorin_ristache »
Hello,
The combo boxes from the two perspectives (Editor and Debugger) are very different. The combo box of the Editor perspective contains only MSXML 4.0 and MSXML.NET as external validation engines and this happens only when the current document is an XSLT stylesheet (for other document types the combo box contains other engines). The default engine used by the action Validate Document for XSLT stylesheets is set from Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT and it can be Saxon, Xalan or a JAXP engine. The combo box of the Debugger perspective contains Saxon and Xalan as transformation engines.
If you want to switch between Saxon and Xalan for transformations you have to edit the transformation scenario associated with the current document and change the selected engine in the Transformer combo box.
Regards,
Sorin
The combo boxes from the two perspectives (Editor and Debugger) are very different. The combo box of the Editor perspective contains only MSXML 4.0 and MSXML.NET as external validation engines and this happens only when the current document is an XSLT stylesheet (for other document types the combo box contains other engines). The default engine used by the action Validate Document for XSLT stylesheets is set from Options -> Preferences -> XML -> XSLT/FO/XQuery -> XSLT and it can be Saxon, Xalan or a JAXP engine. The combo box of the Debugger perspective contains Saxon and Xalan as transformation engines.
If you want to switch between Saxon and Xalan for transformations you have to edit the transformation scenario associated with the current document and change the selected engine in the Transformer combo box.
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