Project

Profile

Help

Bug #3024

closed

Base URI reported for a secondary result document is incorrect.

Added by Michael Kay over 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Internals
Sprint/Milestone:
-
Start date:
2016-11-10
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.7
Fix Committed on Branch:
9.7, trunk
Fixed in Maintenance Release:
Platforms:

Description

See thread started on saxon-help list by Florent Georges. Given an application that supplies an OutputURIResolver, and where the static base URI of the stylesheet is unknown, Saxon is calling the OutputURIResolver.close() method with a Result object whose systemId property is blank. It should set the value according to the rules in the spec:

_The href attribute is optional. The default value is the zero-length string. The effective value of the attribute must be a URI Reference, which may be absolute or relative. If it is relative, then it is resolved against the base output URI.

If the implementation provides an API to access secondary results, then it must allow a secondary result to be identified by means of the absolutized value of the href attribute. In addition, if a final result tree is constructed (that is, if the effective value of build-tree is yes), then this value is used as the base URI of the document node at the root of the final result tree._

Added as JUnit test s9apitest/TestSecondaryDestination

Actions #1

Updated by Michael Kay over 7 years ago

  • Description updated (diff)
Actions #2

Updated by Michael Kay over 7 years ago

  • Category set to Internals
  • Status changed from New to Resolved
  • Assignee set to Michael Kay
  • Applies to branch 9.7, 9.8 added
  • Fix Committed on Branch 9.7, 9.8 added

Fixed with a change to ComplexContentOutputter.makeComplexContentReceiver() to take the systemId from the supplied receiver and set it on the returned receiver.

Also added a change to this method to avoid adding a new CCO to the pipeline if the receiver is already a CCO. But it's a bit more complex if there is also a SkipValidator involved to remove type annotations.

Actions #3

Updated by O'Neil Delpratt over 7 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.7.0.13 added

Bug fix applied in the Saxon 9.7.0.13 maintenance release.

Actions #4

Updated by O'Neil Delpratt almost 7 years ago

  • Applies to branch deleted (9.8)
  • Fix Committed on Branch trunk added
  • Fix Committed on Branch deleted (9.8)

Please register to edit this issue

Also available in: Atom PDF