Add a schemaLanguage parameter to XmlFactories.newSchemaFactory

[ppkarwasz]

Why

XmlFactories.newSchemaFactory() hardcoded W3C XML Schema, while the JAXP API it wraps, SchemaFactory.newInstance(String), lets the caller pick the schema language. Since the library is unreleased there is no compatibility to preserve, so the method itself gains the parameter instead of an overload.

What

• XmlFactories.newSchemaFactory(String schemaLanguage) passes the language through to SchemaFactory.newInstance(String) and propagates its IllegalArgumentException/NullPointerException contract. The hardening is enforced through the factory's LSResourceResolver hook and hardened source rewriting rather than any implementation-specific setting, so the documented guarantees hold for whichever schema language JAXP locates a factory for.
• Call sites in the tests and the site index snippet pass XMLConstants.W3C_XML_SCHEMA_NS_URI.
• SchemaFactoryLanguageTest covers the language-selection contract (an unsupported language surfaces IllegalArgumentException); the working W3C path is exercised by the whole schema suite.

Testing

Full surefire matrix green (84 reports, zero failures); the new test runs in the schema-tagged executions.

🤖 Generated with Claude Code

[garydgregory]

@ppkarwasz
In the future, please use your own fork for PRs, otherwise we might be left with stale branches and who knows what in the canonical repository.

[ppkarwasz]

I recently switched to apache because PRs in the same repository can be stacked, while PRs from forks cannot. #23 and #24 were different: workflow changes cannot be tested from a fork before merging.

I know you prefer avoiding branches in apache, so I only use them for stacked PRs or workflow changes. Enabling delete_branch_on_merge should prevent stale branches, and GitHub makes unlinked branches easy to identify and remove.