Bug #5566
closed
Make sure that post-process applies to all result documents
100%
Description
Martin Honnen reports that we appear to post-process only the primary result document. The spec clearly says it should apply to all result documents.
Creating this bug to track the issue.
Updated by Michael Kay over 2 years ago
- Status changed from New to In Progress
It does appear that post-processing is simply not implemented for secondary result documents.
We allocate a Deliverer based on the requested delivery format (raw, document, or serialized). In each case the method Deliverer.getPrimaryResult() is invoking the post-processor, but the corresponding method resolve() (which handles secondary results) is ignoring it.
Updated by Michael Kay over 2 years ago
Checked the QT3 test cases, they do not exercise the post-process option with secondary result documents.
For the test case supplied (delivery format = document) I think I've fixed it, but need more testing.
Updated by Michael Kay over 2 years ago
I have added test cases fn-transform-85, -86, -87 and made the fixes so these are passing on the 11 branch. Need to regression test.
Updated by Michael Kay over 2 years ago
- Category set to XPath conformance
- Status changed from In Progress to Resolved
- Assignee set to Michael Kay
- Applies to branch 11, trunk added
- Fix Committed on Branch 11, trunk added
Fix now applied to the 12.x branch.
Updated by Debbie Lockett over 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 11.4 added
Bug fix applied in the Saxon 11.4 maintenance release.
Updated by Michael Kay over 2 years ago
- Status changed from Closed to Resolved
- Applies to branch 10 added
- Fix Committed on Branch 10 added
The p[atch has been retro-fitted to the 10.x branch.
Updated by O'Neil Delpratt almost 2 years ago
- Fixed in Maintenance Release 12.0 added
Bug issue fix applied in the Saxon 12.0 Major Release. Leaving this bug marked as Resolved until fix applied to Saxon 10 maintenance release.
Updated by O'Neil Delpratt almost 2 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 10.9 added
Bug fix applied in the Saxon 10.9 maintenance release.
Please register to edit this issue
.