| EclipseXSLT 1.0.3 released [message #289108] |
Fri, 29 July 2005 08:59 |
Eclipse User |
|
|
|
hi,
Open Source Software Orangevolt EclipseXSLT 1.0.3 released.
EclipseXSLT is an Eclipse 3.1 Feature adding XSLT capabilities
and a configurable xml outline to Eclipse.
EclipseXSLT can be used for writing documentation
using docbook or other XSLT based technologies
or developing XSLT stylesheets.
You can download EclipseXSLT at http://sourceforge.net/projects/eclipsexslt.
Documentation is available at http://eclipsexslt.sourceforge.net/index.html
EclipseXSLT requires Eclipse 3.1 and Eclipse Webtools Build I20050711
(or higher).
See http://eclipsexslt.sourceforge.net/chapter-requirements.html for
details.
See http://eclipsexslt.sourceforge.net/chapter-N10275.html for
installing EclipseXSLT via Eclipse Update Manager.
EclipseXSLT is released under the terms of CPL.
Features :
* Launch XSLT transformations by just execute the stylesheet
via Run/Run As ... menu
* Widely configurable XSLT launch configuration.
XSLT launch configurations can be exported to Ant Build Files
* Launch configuration post processing supported. This feature is useful
for generating pdf files or copying media resources after transformation.
Post processing uses Ant build files.
* Handy editor extensions making XML/XSLT editing more comfortable.
* Configurable XML editor outline based on xpath.
Outline configurations for XSLT, DocBook and Orangevolt's
own Documentation format are provided within the feature.
* Syntax colored xslt process console with hyperlink support
for direct jumps to error/warning markers and assigned files
* Pluggable XSLT processor support. Xalan, Saxon and the XSLT Transformer
provided by Java are integrated in the feature. Support for other XSLT
Transformers can easily be added by the user.
* XSLT Transformer Preferences allow indiviual tuning of
output properties and transformer features.
* XPATH Navigator View. Allows executing xpath expressions
based on opened XML documents or selections.
1.0.3 Changes :
2005-07-13 :
successfully ported to eclipse3.1 + wtp-sdk-I20050711
transformer description files now include parameter "classpath" which
may contain a set of plugin relative
or absolute paths directing to xslt processor libraries. the use of
wildcards is allowed for the jar name
(i.e you can write "lib/xalan-*.jar" instead of "lib/xalan-2.6.0.jar" or
"lib/myproc/*.jar" for all jars inside
plugin directory "lib/myproc")
launcher takes "<default>" as transformer option (switch -c) if no
transformer class was specified
(this is also used for the default transformer provided by java runtime).
2005-07-14 :
launcher code modified to match both xalan and saxon requirements. in
detail : saxon expects transformation source
and source xml as full uri (starting with "file:///") and for the result
file xalan expects it too
exception when starting xsltplugin without open xslt editor fixed.
xpath navigator uses (again :-) xalan 2.6.0 xpath engine. jaxen was removed.
2005-07-15 :
custom outline rendering rewritten to be namespace independent.
outline configuration changed so that element attribute can take
multiple root elements
(... <root element="book|part|article"> ... for example)
2005-07-18 :
outline configuration extension point description added but not implemented
outline configurations modified to use extension point
bug fixed for console line tracker. now console line tracker identifies
also file:/
protocol's
huge performance improvement for large xml document outlines by
optimizing findNearestMatchingChildren()
2005-07-19 :
the orangevolt sourcestyle xslt extension is automatically available
when choosing xalan as xslt processor
bug fixed in launch configuration dialog which sometimes resulted in
array-out-of-bounds exceptions
2005-07-20 :
transformer feature configuration added to xslt preferences. xslt
preferences dialog refactored to provide
better user experience.
2005-07-21 :
extension point created for creating dynamically added xsl transformers
(see saxon transformer example).
xslt launcher now understands features and handles them including the
feature type (boolean, string, class, int, object etc.)
2005-07-26 :
launch configuration now can be exported to ant build files. To export
an launch configuration simply open the launch configuration
and click "export configuration" in the main xslt tab.
xslt post processing is now integrated. this feature is configurable via
launch configuration tab "XSLT Post Processing"
and allows you to automatically run an ant build file after the
transformation. this is very useful when generating pdf out of
generated xml-fo files. also further use case is to copy additional
resources (images !!) after transformation.
configuration export wizard modified to support post processing.
many regards,
lars
www.orangevolt.com
|
|
|
Powered by
FUDForum. Page generated in 0.25615 seconds
Home