Re: xsl transform() calls and creating SEF files

Surely if you want to package the two transforms into a single SEF, then you know statically what transformation you want to invoke, and if you know statically what transformation you want to invoke, then you don't need fn:transform()? This sounds like a case for a static invocation using packages rather than a dynamic invocation using fn:transform().

Michael Kay
Saxonica

> On 6 Jul 2021, at 16:17, Graydon Saunders <[email protected]> wrote:
> 
> Hello!
> 
> We generally don't want to make the application any more potentially comprehensible to customers than the insides of a SEF file.  As a result, I'm trying to package an application which both includes a bunch of XSLT files and which calls various XSLT transforms via transform() using:
> 
> java -cp "$SAXON:$RESOLVER:$EXTENSIONS" net.sf.saxon.Transform \
>     -xsl:"$MAIN" \
>     -export:main.sef \
>     -target:PE \
>     -relocate:on \
>     -nogo
> 
> If I try to run the resulting SEF file, it fails, because it can't find the first of the XSLT transforms called via transform().  To the best of my limited ability to tell, that's because that transform didn't make it into the SEF file.
> 
> Is there a way to get the "create a SEF file" process to incorporate all the XSLT transforms referenced by transform() into the SEF file?  Is there some other way to get a monolithic deployable transform? 
> 
> Thanks!
> Graydon
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/saxon-help