Unlicensed SchemaValidator segmentation error
A user recently discovered that instantiating an unlicensed copy of the SchemaValidator does not terminate properly and will eventually lead to a segmentation error if the SchemaValidator object is later used. This can happen where the license file is not present in EE, a call made via PE or HE.
Details on the error and what is produced see https://github.com/rimmartin/saxon-node/issues/7#issuecomment-206097271
In this situation, we need to properly check if an exception is thrown in the constructor. A user can then check this in their code as it is their responsibility to make sure a license file is available and that they are using the correct product.
Please register to edit this issue