I guess there might be a general interest in somehow protecting the Intellectual Property built into a XSL stylesheet. At least I have something like that in mind and planned to investigate that further.
But maybe saving the XSL as a binary XML (PTree) would be enough to block the casual viewer’s eyes?
Am 19.02.2010 um 18:38 schrieb Dimitre Novatchev:
> I have talked to people, who will be interested to have this
> capability as part of SaxonEE.NET and also the (not yet implemented)
> capability of compiling a library of xsl:finction functions.
> Dimitre Novatchev
> On Fri, Feb 19, 2010 at 7:52 AM, Michael Kay <mike@...> wrote:
>> Does anyone use the Saxon-EE feature to compile queries to Java code?
>> I ask because there is almost no feedback on the feature; and I would expect
>> feedback, because I know it's very difficult to test the code thoroughly,
>> and that when I use it myself on new queries from outside the test suite,
>> it's not unusual to find bugs.
>> Maintaining this code and implementing it for new language features is a
>> significant effort, and I have to wonder whether the effort is worthwhile.
>> It typically gives a speed-up of 25%, sometimes 50%, and perhaps there
>> aren't enough people who need that extra performance boost to justify the
>> effort of using the feature. Or perhaps people tried it, found problems, and
>> didn't report them?
>> I know, of course, that replacing it with something that works with no
>> effort on the part of the user (directly compiling critical parts of a query
>> to bytecode on-the-fly) would be much better. But that's also a significant
>> amount of work.
>> Michael Kay
Michael Müller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lösungen und Training, FrameScript, XML/XSL, Unicode
Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747