Bug Fix Report
Generate a Fixed Bugs Report for a single version, or for all bugs fixed between any two versions (inclusive).
| Found 4 bugs fixed in 10.0-2.1 |
| Bug ID | Component | Platform | Status |
| XSLT-DEFAULTCOLL erroneously raised when not all default-collations are unrecognized | |||
| If an XSLT stylesheet includes a default-collations attribute with multiple collations, and any one of them is unrecognized, XSLT-DEFAULTCOLL will be raised, even if some other collation in the list is recognized. | |||
| BUG-53134 | XSLT | all | Fixed in 10.0-2.1 |
| Support ARN's for AWS KMS | |||
| Please note that starting with 9.0-10.3 and 10.0-2.1, users will be able to use encryption keys having the ARN syntax when specifying AWS-KMS key IDs. This allows you to specify keys from other AWS accounts. Previously, this was not supported. | |||
| BUG-53230 | Encryption at REST | all | Fixed in 10.0-2.1 |
| XSLT reports bogus XSLT-APPTEMPCTXNOTNODE | |||
| Under some circumstances involving a template with a complex body that includes evaluation of an XPath that end with a value step (not a node step), XSLT may incorrectly raise the error XSLT-ATTTEMPCTXNOTNODE. This may manifest in Schematron processing also. | |||
| BUG-53235 | XSLT | all | Fixed in 10.0-2.1 |
| Calling gradle mlUpdateIndexes on artifact produced from gradle hubSaveIndexes fails | |||
| The gradle call mlUpdateIndexes fails on an artifact produced from gradle hubSaveIndexes with an error saying that the lexical value "zxx" is not valid for dbprop:language. | |||
| BUG-53169 | Entity Services | all | Fixed in 10.0-2.1 |