This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24334 - [XT3TS] Streaming tests for try/catch
Summary: [XT3TS] Streaming tests for try/catch
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Abel Braaksma
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2014-01-20 17:10 UTC by Michael Kay
Modified: 2015-05-06 21:14 UTC (History)
1 user (show)

See Also:


Description Michael Kay 2014-01-20 17:10:31 UTC
The tests in strm/si-try are written in the mistaken belief that the specification allows try/catch to be streamable. The current (Dec 2013) spec does not.
Comment 1 Abel Braaksma 2014-01-23 12:50:40 UTC
The current draft says, about xsl:try:

"If the select expression and/or sequence constructor of the xsl:catch element are motionless, then the sweep of the select expression and/or sequence constructor of the xsl:try element (whichever is present);"

In other words, if <xsl:catch select="motionlessexpr" />, then the body of the xsl:try is streamable, otherwise it is ree-ranging. 

Going over the tests it seems that all tests are written with xsl:catch having a grounded and motionless expression, meaning that the streamability of the xsl:try body applies. From what I glanced over, it looks like they are written correctly.

I'm not sure where in the spec it should say that this is non-streamable.
Comment 2 Abel Braaksma 2014-09-15 02:51:21 UTC
Meanwhile, the try/catch and its streamability features have received quite some discussion in the working group and many changes have been applied to the spec to accommodate streamable try/catch using the new @rollback-output attribute (see, members only).

I will move forward and close this bug report, it seems to have been taken over by events, but feel free to reopen if I'm mistaken.
Comment 3 Abel Braaksma 2015-05-06 21:14:44 UTC
Was resolved > 30 days ago, closing.