I don't think I'll be able to fix this without seeing a stylesheet that
reproduces the problem.
It looks as if the first stylesheet is producing output that isn't a
complete document. If this turns out to be the case, it's possible that the
best I can do is to document a restriction and have the code fail more
cleanly when the situation occurs. But I'm guessing, there's not really
enough here to go on.
I don't have very many tests of next-in-chain, but the ones I do have are
Have you applied any published patches to the code? I'm asking just in case
any of them might have introduced a regression.
> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...] On Behalf Of
> Jens Stavnstrup
> Sent: 16 March 2005 12:55
> To: saxon-help@...
> Subject: [saxon] Failure using 8.3B and next-in-chain attribute
> Piping output from one stylesheet to another fails with SaxonB 8.3
> using the saxon:next-in-chain attribute fails withe the following
> error. And yes the first stylesheet works just fine, without the
> saxon:next-in-chain attribute.
> at net.sf.saxon.Controller.transform(Controller.java:977)
> at net.sf.saxon.Transform.processFile(Transform.java:788)
> at net.sf.saxon.Transform.doMain(Transform.java:467)
> at net.sf.saxon.Transform.main(Transform.java:59)
> Fatal error during transformation: null
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from
> real users.
> Discover which products truly live up to the hype. Start reading now.
> saxon-help mailing list