Skip to content

chore(deps-dev): bump com.helger.maven:ph-schematron-maven-plugin from 10.0.1 to 10.0.2 - #1315

Merged
duncdrum merged 1 commit into
masterfrom
dependabot/maven/com.helger.maven-ph-schematron-maven-plugin-10.0.2
Sep 11, 2026
Merged

duncdrum merged 1 commit into
masterfrom
dependabot/maven/com.helger.maven-ph-schematron-maven-plugin-10.0.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 11, 2026

Copy link
Copy Markdown
Contributor

Bumps com.helger.maven:ph-schematron-maven-plugin from 10.0.1 to 10.0.2.

Release notes

Sourced from com.helger.maven:ph-schematron-maven-plugin's releases.

v10.0.2

  • (pure) Foreign (non-Schematron) elements are now reported as warnings - fixes #186. The pure XPath engine (SchematronResourcePureXPath) can only evaluate Schematron elements and XPath expressions, so elements from other namespaces - typically XSLT ones like <xsl:function> or <xsl:variable> - were silently ignored so far. Now one warning per foreign element is sent to the configured IPSErrorHandler when the schema is bound, naming the element and its namespace URI. Use SchematronResourcePureXslt or one of the XSLT based engines if the XSLT elements need to be evaluated. The new helper PSForeignElementVisitor.forEachForeignElement (PSSchema, BiConsumer) in ph-schematron-model performs the underlying model walk and is engine independent.
  • New SaxonDOMSource to opt into Saxon's native tree model for DOM based validation - see #198. When an XML instance is passed to an XSLT based engine as a javax.xml.transform.dom.DOMSource, Saxon wraps the DOM and evaluates every XPath step against that wrapper. For large documents - in particular ones with long sibling lists - this repeated navigation dominates the validation runtime. The new class com.helger.schematron.saxon.SaxonDOMSource in ph-schematron-api is a DOMSource subclass that acts as a marker: pass it instead of a plain DOMSource to applySchematronValidation (Source), applySchematronValidationToSVRL (Source) or getSchematronValidity (Source) and the engine builds the transformer's configured native Saxon tree once per validation, instead of navigating the wrapped DOM. The Node based overloads always create a plain DOMSource, so one of the Source based methods must be used to opt in. All XSLT based engines honour it - SchematronResourceXSLT, SchematronResourceSCH, SchematronResourceSchXslt_XSLT2 and SchematronResourceSchXslt2 - but only if the wrapped node is a Document and the running transformer is a Saxon one. In every other case it behaves exactly like a regular DOMSource. The original DOM is never modified and the converted tree is not cached, so a single SaxonDOMSource can be reused across validations and across engines with different Saxon configurations, and later modifications of the DOM are picked up by the next validation. Because the transformation runs on a snapshot, two semantics differ from a regular DOMSource: DOM object identity is not retained, and base URIs are resolved against the source's system ID while the tree is built. Stay with a regular DOMSource if the stylesheet or an extension function requires the original DOM nodes or the wrapped DOM behaviour. This is purely opt-in - existing code keeps the previous wrapped DOM behaviour.

What's Changed

New Contributors

Full Changelog: phax/ph-schematron@ph-schematron-parent-pom-10.0.1...ph-schematron-parent-pom-10.0.2

Commits

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
com.helger.maven:ph-schematron-maven-plugin [>= 8.a, < 9]

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [com.helger.maven:ph-schematron-maven-plugin](https://github.com/phax/ph-schematron) from 10.0.1 to 10.0.2.
- [Release notes](https://github.com/phax/ph-schematron/releases)
- [Commits](phax/ph-schematron@ph-schematron-parent-pom-10.0.1...ph-schematron-parent-pom-10.0.2)

---
updated-dependencies:
- dependency-name: com.helger.maven:ph-schematron-maven-plugin
  dependency-version: 10.0.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Sep 11, 2026
@duncdrum
duncdrum merged commit 0ee903f into master Sep 11, 2026
2 checks passed
@duncdrum
duncdrum deleted the dependabot/maven/com.helger.maven-ph-schematron-maven-plugin-10.0.2 branch September 11, 2026 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant