Skip to content

make XPathFactory configurable in Hamcrest Matcher and AssertJ assertions #131

@bodewig

Description

@bodewig

While org.xmlunit.xpath.JAXPXPathEngine allows users to specify an instance of XPathFactory explicitly, this is not exposed to the Hamcrest matchers or the AssertJ assertions.

Looking around Saxon because of #130 I realized Saxon has opted out of using the service loader mechanism and asks users to create the factory explicitly[1]. This means using Saxon is not easily possible with matchers/assertions.

[1] http://www.saxonica.com/documentation/index.html#!xpath-api/jaxp-xpath/factory

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions