XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2016)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
erik meissnerSubject: 2007 R2 Java built-in XSLT
Author: erik meissner
Date: 04 May 2007 10:02 AM
Hello,

the change from Xalan interpretative processor to built-in Xalan-XSLTC breaks almost every XSLT scenario we are using. The XSLTC does not (?) support extensions like

> dynamic EXSLT extensions
> NodeInfo extension functions
> SQL library extension
> pipeDocument extension
> evaluate extension
> tokenize extension

or they habe a different behaviour.
Why have you changed this? With this change the actual version of Stylus Studio is almost useless for us (and we are afraid also the following versions will be?).

Kind regards,
Erik

Posttop
Ivan PedruzziSubject: 2007 R2 Java built-in XSLT
Author: Ivan Pedruzzi
Date: 04 May 2007 12:01 PM
Hi Erik,

You can still use any XalanJ version configured as custom processor.

See Tools -> Options -> Module Settings -> XSLT Editor -> Processor Settings -> custom

Set the command line to
java org.apache.xalan.xslt.Process -in %1 -xsl %2 -out %3

set the Classpath accordingly


Hope this helps
Ivan Pedruzzi
Stylus Studio Team

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.