Can you elaborate on this David? Is this a proprietary processor, or open
source? url? What do the Xalan guys think about this, are they going to EOL
Xalan or are they waiting for resources to catch up to 2.0?
--- On Tue, 10/11/09, David Carver wrote:
> From: David Carver
> Subject: Re: Xa
And unfortunately, IBM which provided the original basis for Xalan has
decided to do their own XSLT 2.0 processor instead of making Xalan XSLT
2.0 capable. Even though there is code in Apache's source code control
system that has the basis for XSLT 2.0 support.
Dave
Mukul Gandhi wrote:
On T
On Tue, Nov 10, 2009 at 9:09 AM, Andy Chambers
wrote:
> As always, it depends on your usage but saxon is pretty well optimized
> and worked significantly faster in benchmarks we created for our typical
> usage.
Personally speaking, I haven't observed any slowness with Xalan. I
haven't seen any in
On Tue, Nov 10, 2009 at 3:32 AM, Mukul Gandhi wrote:
> On Tue, Nov 10, 2009 at 7:59 AM, Adam Jenkins
>
>
>> 2) Slow Performance (relative to Saxon)
>
> I don't think Xalan is slower, as compared to Saxon or any other XSLT
> engine, if you are working in XSLT 1.0 mode.
As always, it depends on yo
On Tue, Nov 10, 2009 at 7:59 AM, Adam Jenkins
> 2) Slow Performance (relative to Saxon)
I don't think Xalan is slower, as compared to Saxon or any other XSLT
engine, if you are working in XSLT 1.0 mode.
Xalan also provides, XSLTC (ref,
http://xml.apache.org/xalan-j/xsltc_usage.html) which allow
I mean "The reasons always quoted for NOT choosing xalan are"...
--- On Tue, 10/11/09, Adam Jenkins wrote:
> From: Adam Jenkins
> Subject: XalanJ future
> To: xalan-dev@xml.apache.org
> Received: Tuesday, 10 November, 2009, 1:29 PM
> Hi Guys,
>
> A bit off topic here, but I wanted to ask a que
Hi Guys,
A bit off topic here, but I wanted to ask a question about the future of
XalanJ. As a java consultant of many years, I've always used xalan extensively
and like it above saxon...I've even pushed the extension element and extension
functions framework quite heavily over the years. Any
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774965#action_12774965
]
John commented on XALANJ-656:
-
[bet
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla/a
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774966#action_12774966
]
John commented on XALANJ-656:
-
[beste
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774965#action_12774965
]
John commented on XALANJ-656:
-
[bet
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla/a
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774966#action_12774966
]
John commented on XALANJ-656:
-
[beste
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774960#action_12774960
]
John commented on XALANJ-656:
-
[beste
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla
[
https://issues.apache.org/jira/browse/XALANJ-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774960#action_12774960
]
John commented on XALANJ-656:
-
[beste
casino|http://devel-rok.informatik.hu-berlin.de/bugzilla
13 matches
Mail list logo
