Bug #4784

Register specific CollectionFinder class with Saxon configuration file

Added by Nico Kutscherauer over 1 year ago. Updated about 1 year ago.

Start date:
Due date:
% Done:


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



As described on the Saxon documentation page, I should be able to create my own class for resolving URIs for the funcitons fn:collection() and/or fn:uri-collection():

I would like to use this, but I have to configure the Saxon by a config file. If I understand your example config correctly, I would have to set the attribute /configuration/global/@collectionFinder (!configuration/configuration-file). Unfortunatelly this attribute seems to have no effect.

After debugging I have to assume, that the ConfigurationReader ignores this attribute completely and that it is currently not possible to configure this feature using a config file. Am I right or have I missed something?

Best Regards, Nico

PS: I'm currently using Saxon 9.9.1-5, but I checked also the source code of the ConfigurationReader in Saxon 10-2 and I could find a change for the collectionFinder attribute.


#1 Updated by Michael Kay over 1 year ago

Indeed, it appears that this attribute was added to the documentation and to the configuration file schema, but not to the configuration reader or its test cases.

#2 Updated by Michael Kay over 1 year ago

Added JUnit test s9apiTest.TestCollections.testCollectionFinderConfigFile.

One-line fix in ConfigurationReader.readGlobalElement: add

applyProperty(props, "collectionFinder", Feature.COLLECTION_FINDER_CLASS);

#3 Updated by Michael Kay over 1 year ago

  • Category set to Configuration
  • Status changed from New to Resolved
  • Assignee set to Michael Kay
  • Priority changed from Low to Normal
  • Applies to branch trunk added
  • Fix Committed on Branch 10, trunk added

Fixed on the 10.x and development branches

#4 Updated by O'Neil Delpratt about 1 year ago

Bug fix applied in the Saxon 10.3 maintenance release

#5 Updated by O'Neil Delpratt about 1 year ago

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

Please register to edit this issue

Also available in: Atom PDF