validator/CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

Unreleased

1.3.1

Fixed

• getFailedAsserts() and isSchematronValid() in DefaultResult.java do not reflect actual schematron validation result
• processing aborts on schematron execution errors (e.g. errors within schematron logic). The validator now generates a report in such cases.
• exception while resolving when using XSLT's unparsed-text() function within report generation

Added

• [CLI] add summary report

Changed

• engine info contains version number of the validator (configurations can output this in the report for maintainance puposes)
• options to customize serialized report file names (cmdline only) via --report-prefix and --report-postfix
• remove unused dependency Apache Commons HTTP

1.3.0

Added

• Added a builder style configuration API to configure scenarios
• Added an option to configure xml security e.g. to load from http sources or not from a specific repository (so loading is configurable less restrictive, default strategy is to only load from a local repository)
• Support java.xml.transform.Source as Input

Changed

• Inputs are NOT read into memory (e.g. Byte-Array) prior processing within the validator. This reduces memory consumption.
• Overall processing of xml files is based on Saxon s9api. No JAXP or SAX classes are used by the validator (this further improves performance and memory consumption)

Deprecations

• CheckConfiguration is deprecated now. Use Configuration.load(...) or Configuration.build(...)

1.2.1

Fixed

• Validator is creating invalid createReportInput xml in case of no scenario match

1.2.0

Added

• Provide access to schematron result through Result.java
  • Result#getFailedAsserts() returns a list of failed asserts found by schematron
  • Result#isSchematronValid() convinience access to evaluate whether schematron was processed without any FailedAsserts

Changed

• Result#getAcceptRecommendation() does not only work when acceptMatch is configured in the scenario
  • schema correctness is a precondition, if the checked instance is not valid, this evaluates to REJECTED
  • if acceptMatch is configured, the result is based on the boolean result of the xpath expression evaluated against the generated report
  • if no acceptMatch is configured, the result is based on evaluation of schema and schematron correctness
  • UNDEFINED is only returned, when processing is stopped somehow
• Result#isAcceptable() can now evaluate to true, when no acceptMatch is configured (see above)

1.1.3

Fixed

• XXE vulnerability when reading xml documents with Saxon #44
• validator unintentionally stopped when schematron processing has errors. See #41.

1.1.2

Fixed

• NPE in Result.getReportDocument for malformed xml input

1.1.1

Added

• Convenience method for accessing information about well-formedness in Result
• Convenience method for accessing information about schema validation result in Result

Fixed

• NPE when validating non-XML files

1.1.0

Added

• Enhanced API-Usage e.g. return Result object with processing information
• Support loading scenarios and content from a JAR-File
• Simple Daemon-Mode exposing validation functionality via http
• cli option to serialize the 'report input' xml document to cwd (current working directory)
• Documentation in docs folder

Changed

• Use s9api (e.g. XdmNode) internally for loading and holding xml objects (further memory optimization)
• Builds with java 8 and >= 11
• Packages for java8 and java >= 11 (with jaxb included)
• Translated README.md

1.0.2

Fixed

• Memory issues when validating multiple targets

1.0.1

Changed

• Removed XRechnung configuration from release artifacts and source (moved to own repository )

1.0.0

• Initial Release