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.
Xalan3 XSLT 2.0 XPath 2.0 support?

Xalan3 XSLT 2.0 XPath 2.0 support?

2007-07-31       - By Eric J. Schwarzenbach
Reply:     1     2     3     4     5     6  

My company also is moving toward switching to Saxon, even if only the
free version, for XSLT 2.0 support, as well as expected performance
gains (though whether the free, open-source Saxon-B also out-performs
Xalan, as the commercial Saxon-SA seems to, is not clear to me;
certainly comments from Xalan folk on that matter would be of interest).

I must say lack of even any public statement of intentions in the web
site, with regard to XSLT 2.0, as well as the 6 month silence between
the delay of the intended 2.71 version and the next mention of it, has
made us wonder seriously about the future of Xalan. I don't say this to
be critical of the folks generously giving their time to this project,
but just to point out what appearances may be saying (correctly or
incorrectly) to people assessing the competitiveness of the the XSLT
products out there.

Eric Schwarzenbach



Matthew L. Avizinis wrote:
> my 2ยข worth:
> I for one would like to see this.  I've played around with Saxon and
> find that xslt2 is easier to write, read, and maintain.  I've been
> thinking about switching a project I've been working on where I work to
> Saxon for this reason (among others), but I'd miss the nice
> extensibility that Xalan has with its scriptable Java/Javascript (makes
> it nice to include processor extension functions right in a stylesheet)
> and its exslt support.
> Unfortunately, wouldn't be able to contribute much other than reporting
> potential bugs when encountered.
> Matthew L. Avizinis
> Gleim Publications, Inc.
>
> Henry Zongaro wrote:
>  
>> Hi, Johannes.
>>
>> I'm cross-posting to both mailing lists to make sure we have broad
>> coverage for this discussion.  Everyone, please follow up on
>> xalan-j-users.
>>
>> Johannes Neubauer <johannes.neubauer@(protected)> wrote on
>> 2007-07-24 09:57:53 AM:
>>    
>>> Will future releases of Xalan-J definitively support XSLT 2.0 and XPath
>>> 2.0?
>>>
>>> I searched the user and dev mailing lists and found only 4 year old
>>> postings that say that there will be XSLT 2.0 implementations in future
>>> Xalan-J Releases. Furthermore I found the xslt20/ and xslt20-compiled/
>>> branches in the SVN repositories, but 4 years passed since the last
>>> checkin, too.
>>>      
>> Speaking as a committer on the Apache Xalan project, I'd certainly be
>> interested in seeing an XSLT 2.0 implementation take shape here.  I'd
>> like to find out how much interest there is from others in seeing an
>> open source XSLT 2.0 implementation from the ASF.  If you're
>> interested in such an implementation (as a user), please respond and
>> let us know which features you're most interested in.  And conversely,
>> I would also like to hear from any users who are satisfied with an
>> XSLT 1.0 processor, and not much interested in migrating to XSLT 2.0.
>>
>> Feel free to respond either on the mailing list or to me directly, in
>> private.  I'll summarize the results of this informal polling in a
>> week or so.
>>
>>    
>>> In another mail-archive (not in a apache related) I found a posting that
>>> claimed that a apache programmer has said that there won't come any
>>> implementations for the new specifications, because the management does
>>> not agree with them.
>>>      
>> For the benefit of the list, I thought I should mention that you told
>> me in a private e-mail that you later realized it was a developer on a
>> different XSLT processor (not an Apache Xalan developer) who said they
>> had no interest in XSLT 2.0.
>>
>> Thanks,
>>
>> Henry
>> ------------------------------------------------------------------
>> Henry Zongaro      XSLT Processors Development
>> IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
>> mailto:zongaro@(protected)
>>    
>
>