Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #5566

closed

Make sure that post-process applies to all result documents

Added by Norm Tovey-Walsh almost 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Low
Assignee:
Michael Kay
Category:
XPath conformance
Sprint/Milestone:
-
Start date:
2022-06-14
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 11, trunk
Fix Committed on Branch:
10, 11, trunk
Fixed in Maintenance Release:
11.4, 12.0, 10.9
Platforms:

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.

Actions
Copy link
 #1

Updated by Michael Kay almost 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.

Actions
Copy link
 #2

Updated by Michael Kay almost 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.

Actions
Copy link
 #3

Updated by Michael Kay almost 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.

Actions
Copy link
 #4

Updated by Michael Kay almost 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.

Actions
Copy link
 #5

Updated by Debbie Lockett almost 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.

Actions
Copy link
 #6

Updated by Michael Kay over 1 year 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.

Actions
Copy link
 #7

Updated by O'Neil Delpratt over 1 year 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.

Actions
Copy link
 #8

Updated by O'Neil Delpratt about 1 year 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

Actions
Send by e-mail Copy link

Also available in: Atom PDF