opendfdl / examples Goto Github PK

Integrated extension functions is an alternative way in Saxon to implement Java extensions to XSLT/XPath, rather than the reflexive extension functions used now. The link discribes multiple advantages to integrated vs reflexive, but an additional advantage is that integrated extensions are support in Saxon-HE. This means we can update build.sbt to depend on Saxon-HE, making it easier to quickly jump into modifing this, and adding it to regression suites.

The dfdlParse function returns the XML infoset as a string and then uses the parse-xml() function to convert that to a node that the XSLT can work on. Rather than returning a string, the dfdlParse funtion should just directly return a node to avoid this string-to-node conversion.

A useful feature would be a cache of the compiled DFDL schema so that the penalty
to compile it isn't being paid every time you run the XSLT. (Something many
usages of Daffodil need - probably should be a feature supplied in a Daffodil
library so that it's not being reinvented.) Daffodil compilation times are
acceptable now for long-running processes, but not for quick start/stop things
as XSLT commonly is.

It would be nice if this weren't XSLT daffodil java function weren't dependant on Saxon's implementation. If Java XSLT has a way to handle this, and if it's compatible with XSLT, that might be a preferred method to implementation a DFDL XSLT function.

The helloWorld example shows parse, unparse, XPath, and XSLT, but not XQuery. Should show XQuery too, or another example should.