Re: XSLT help wanted [Was: FOPRunXSLTExt for Antenna House]

On Thu, January 2, 2014 5:25 am, Arved Sandstrom wrote:
> I can help with this, Tony. The requirement to switch between
> implementations is like bread and butter for a FT developer. :-) I'll
> rely on you and others to correct me on any naive use of XSLT; as far as
> API design goes, or use of C/C++/Java/C#/F# (you get the drift) I can
> deal with that.

Thanks for offering.  I think we still need an external XSLT module for
calling the extension function just so it's easier for other people to use
the extension in real stylesheets without having to worry too much about
the details.

The part I've been meaning to talk to you about is, firstly, changing the
function signature for the FOP function to just return the area tree as a
document-node() along the lines of the AHF function and, secondly and more
importantly, making a jar or jars so that the functions work with multiple
versions of Saxon.

If you compare the current RunFOPSaxon.java [1] written against Saxon 9.4
and the current RunAHFSaxon.java [2] written against Saxon 9.5 because I
was casting around for (IIRC) how to return a document-node(), the version
for Saxon 9.4 uses net.sf.saxon.value.Value, which isn't in the Saxon 9.5
API [3].

I haven't actually looked to see whether it's possible to write both
classes in a version-neutral way, but if that's not possible, how, with
NetBeans, is it possible to produce multiple jars compiled against
different versions of a library jar?  All that I've been able to think of
so far is to maintain multiple NetBeans projects, one for each Saxon
version.  What would you do?

Regards,


Tony.

[1]
https://dvcs.w3.org/hg/ppl/file/506709a9527e/FOPRunXSLTExt/src/org/w3c/ppl/xslt/ext/fop/saxon/RunFOPSaxon.java
[2]
https://dvcs.w3.org/hg/ppl/file/506709a9527e/FOPRunXSLTExt/src/org/w3c/ppl/xslt/ext/ahf/saxon/RunAHFSaxon.java
[3] http://www.saxonica.com/documentation/javadoc/index.html

Received on Thursday, 2 January 2014 10:52:33 UTC