<div dir="ltr">from their website<br><br><font face="Arial, Helvetica, sans-serif"><p><font face="Arial, Helvetica, sans-serif">Saxon-HE 9.6</font></p>"The open-source implementation of XSLT 2.0, and XPath 2.0 and 3.0,
and XQuery 1.0 and 3.0. This provides the "basic" conformance level of these languages; it also
supports some optional features of the specifications such as serialization and support for XQuery modules.<p></p>
<p>Not included in the Home Edition are: schema processing and schema aware XSLT and XQuery;
support for higher-order functions; numerous Saxon extensions; calling out to
Java methods; XQuery Update support; various optimizations including join optimization; streamed processing;
and byte code generation."</p></font><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 29, 2015 at 3:46 PM, David M. Lloyd <span dir="ltr"><<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It was proposed to consider switching to Saxon, since Xalan has<br>
basically been dead since 2007. Saxon apears to include a<br>
TransformerFactoryImpl (though I don't have any idea as to completeness<br>
of compatibility).<br>
<div class="HOEnZb"><div class="h5"><br>
On 05/29/2015 08:30 AM, Jason T. Greene wrote:<br>
> The only reason we need Xalan is to provide a jaxp impl of transformer. Ideally we could just rely on the JDK, which uses a fork of xalan, but the translet code which is compiled by it is not compatible with modular classloading. So we just need that one patch. As of late the JDK fork is more current, so we could potentially switch to a fork of it instead. Since Java 9 is moving to modularity, I imagine they would fix the same issue, we could also send them a patch.<br>
><br>
>> On May 29, 2015, at 8:21 AM, Carlo de Wolf <<a href="mailto:cdewolf@redhat.com">cdewolf@redhat.com</a>> wrote:<br>
>><br>
>> We are keeping a (old) fork around for Xalan. Now and then the question<br>
>> pops whether we can backport more from upstream. Rather I want to rid of<br>
>> it at all as I don't want to maintain forks of third party projects and<br>
>> I don't see Xalan releasing soon with anything we would upstream.<br>
>><br>
>> Can we remove Xalan? (Maybe we have some weird dependency on specifics.)<br>
>> What should be its replacement?<br>
>><br>
>> Filed <a href="https://issues.jboss.org/browse/WFLY-4704" target="_blank">https://issues.jboss.org/browse/WFLY-4704</a> to note any decisions.<br>
>><br>
>> Carlo<br>
>> _______________________________________________<br>
>> wildfly-dev mailing list<br>
>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
- DML<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>