Change in behavior of @saxon:next-in-chain in 9.6 -- intentional or bug?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Change in behavior of @saxon:next-in-chain in 9.6 -- intentional or bug?

Sewell, David R. (drs2n)
Not sure whether to file this with support as a bug, but in case others rely on
similar functionality I thought I'd start with the list.

I have an XSLT transform that was working in Saxon PE 9.4 and 9.5 but breaks in
9.6. I have two transforms, call them T1.xsl and T2.xsl. T1.xsl uses the
extension attribute @saxon:next-in-chain on <xsl:output> to pipe its output to
T2.xsl.

T1.xsl uses <xsl:result.document> to split a single input file into multiple
output files.

I have never had problems with this previously: I put input documents in a
source directory, run the chained transforms, and output documents are
transformed, split and written with the desired filenames to an output
directory.

With PE 9.6, the chain breaks and I get the error message "No source document
has been built by the previous pipeline stage".

So I'm wondering: is @saxon:next-in-chain not intended to support this use case,
or does this look like buggy behavior? (In which case I'll open a bug tracker
ticket.)

David

--
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: [hidden email]   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Reply | Threaded
Open this post in threaded view
|

Re: Change in behavior of @saxon:next-in-chain in 9.6 -- intentional or bug?

Michael Kay
There was no intentional change, but the implementation was considerably affected by internal reorganisation of the code, and there are only a handful of regression tests for the feature, so it doesn't surprise me if something has broken. To investigate, we'll need a repro.

Michael Kay
Saxonica
[hidden email]
+44 (0) 118 946 5893




On 5 Feb 2015, at 19:29, David Sewell <[hidden email]> wrote:

> Not sure whether to file this with support as a bug, but in case others rely on
> similar functionality I thought I'd start with the list.
>
> I have an XSLT transform that was working in Saxon PE 9.4 and 9.5 but breaks in
> 9.6. I have two transforms, call them T1.xsl and T2.xsl. T1.xsl uses the
> extension attribute @saxon:next-in-chain on <xsl:output> to pipe its output to
> T2.xsl.
>
> T1.xsl uses <xsl:result.document> to split a single input file into multiple
> output files.
>
> I have never had problems with this previously: I put input documents in a
> source directory, run the chained transforms, and output documents are
> transformed, split and written with the desired filenames to an output
> directory.
>
> With PE 9.6, the chain breaks and I get the error message "No source document
> has been built by the previous pipeline stage".
>
> So I'm wondering: is @saxon:next-in-chain not intended to support this use case,
> or does this look like buggy behavior? (In which case I'll open a bug tracker
> ticket.)
>
> David
>
> --
> David Sewell, Editorial and Technical Manager
> ROTUNDA, The University of Virginia Press
> PO Box 400314, Charlottesville, VA 22904-4314 USA
> Email: [hidden email]   Tel: +1 434 924 9973
> Web: http://rotunda.upress.virginia.edu/
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help 


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help 
Reply | Threaded
Open this post in threaded view
|

Re: Change in behavior of @saxon:next-in-chain in 9.6 -- intentional or bug?

Sewell, David R. (drs2n)
OK, will submit to bug tracker today or tomorrow, thanks.


On Thu, 5 Feb 2015, Michael Kay wrote:

> There was no intentional change, but the implementation was considerably affected by internal reorganisation of the code, and there are only a handful of regression tests for the feature, so it doesn't surprise me if something has broken. To investigate, we'll need a repro.
>
> Michael Kay
> Saxonica
> [hidden email]
> +44 (0) 118 946 5893
>
>
>
>
> On 5 Feb 2015, at 19:29, David Sewell <[hidden email]> wrote:
>
>> Not sure whether to file this with support as a bug, but in case others rely on
>> similar functionality I thought I'd start with the list.
>>
>> I have an XSLT transform that was working in Saxon PE 9.4 and 9.5 but breaks in
>> 9.6. I have two transforms, call them T1.xsl and T2.xsl. T1.xsl uses the
>> extension attribute @saxon:next-in-chain on <xsl:output> to pipe its output to
>> T2.xsl.
>>
>> T1.xsl uses <xsl:result.document> to split a single input file into multiple
>> output files.
>>
>> I have never had problems with this previously: I put input documents in a
>> source directory, run the chained transforms, and output documents are
>> transformed, split and written with the desired filenames to an output
>> directory.
>>
>> With PE 9.6, the chain breaks and I get the error message "No source document
>> has been built by the previous pipeline stage".
>>
>> So I'm wondering: is @saxon:next-in-chain not intended to support this use case,
>> or does this look like buggy behavior? (In which case I'll open a bug tracker
>> ticket.)
>>
>> David
>>
>> --
>> David Sewell, Editorial and Technical Manager
>> ROTUNDA, The University of Virginia Press
>> PO Box 400314, Charlottesville, VA 22904-4314 USA
>> Email: [hidden email]   Tel: +1 434 924 9973
>> Web: http://rotunda.upress.virginia.edu/
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media, is your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more. Take a
>> look and join the conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> saxon-help mailing list archived at http://saxon.markmail.org/
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/saxon-help
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> saxon-help mailing list archived at http://saxon.markmail.org/
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/saxon-help
>

--
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 400314, Charlottesville, VA 22904-4314 USA
Email: [hidden email]   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
[hidden email]
https://lists.sourceforge.net/lists/listinfo/saxon-help