Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
XSLT-process 2.2 available

XSLT-process 2.2 available

2003-01-08       - By Ovidiu Predescu

What is it?
===========

XSLT-process is a mode for GNU Emacs/XEmacs which transforms it into a
powerful editor with XSLT processing and debugging capabilities. With
this mode you can:

- run an XSLT processor on the Emacs buffer you edit, and view the
results either in another Emacs buffer or in a browser.

- run an XSLT processor in debug mode and view what happens during the
XSLT transformation. You can set breakpoints, run step by step into
your stylesheet, view global and local XSLT variables and many more. In
this mode you effectively use GNU Emacs/XEmacs as an XSLT debugger.

- when used with the DocBook-XSL package, GNU Emacs/XEmacs becomes a
powerful DocBook processing system.

Currently the Saxon and Xalan Java XSLT processors, and Apache FOP are
supported, and the mode comes out of the box configured to use them.

The package has been tested with various versions of XEmacs and GNU
Emacs under Linux, Windows 2000 and MacOS X.

The package is free software and is distributed under GPL. The home
page of XSLT-process is located at:

http://xslt-process.sourceforge.net/

What's new?
===========

This release adds several improvements to the previous release:

- XSLT-process now uses Saxon 6.5.2, Xalan 2.4.1 and FOP 0.20.4

- Debugging using Xalan 2.4.1 is now fully supported.

- Both JDK 1.3 and 1.4 are supported.

- During debugging sessions the output produced by executing the
stylesheet is serialized immediately, then displayed and incrementally
updated in an Emacs buffer.

- Added parameter passing to the XSLT processor. These are parameters
that are specified to all the stylesheets, in addition to any other
parameters. They are specified through the customization menu.

- Logging output, error messages, etc. generated by the FOP processor
are displayed in the *Messages* buffer. The level of logging can be
customized.

- Improvements to the display of information during debugging.

- MacOS X is now a supported platform, in addition to Linux and Windows
2000.


Enjoy,
--
Ovidiu Predescu <ovidiu@(protected)>
http://webweavertech.com/ovidiu/weblog/