serialize-with-legacy-jettison-format
Section: settings
Default Value: true
Valid Values: true, false
Changes Take Effect: if json-hierarchical-driver=false
Setting the option json-hierarchical-driver=false ensures GRE responses with backward compatibility. No other changes is required from the customer if json-hierarchical-driver is false. This option is not applicable if json-hierarchical-driver=true.
9.0.002.01
Genesys Rules System Rules Engine Release Notes
Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
---|---|---|---|---|---|---|---|
03/15/24 | Update | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Upgraded the following libraries to fix CVE-2022-40156, CVE-2022-40155, CVE-2022-40154, CVE-2022-40153, CVE-2022-40151, CVE-2021-39154 vulnerabilities:
- Xstream library to v1.4.20
- Jettison library to v1.5.4
As part of Xstream and Jettison library upgrades, customer may need to utilize the GRE templates available in GRE 9.0.002.01 version. In the current version templates, a new configuration option serialize-with-legacy-jettison-format has been introduced in GRE to maintain backward compatibility with GRE response.
We strongly recommend that customers adapt their applications, which consume GRE, to the GRE response schema produced when json-hierarchical-driver=true. In future releases, GRE response schema produced with json-hierarchical-driver=false will no longer be available.
Recommended Action: Customers are advised to update json-hierarchical-driver=true in non production environment and modify their application to consume GRE response schema produced with this updated option. In future releases, only this schema will be available. As an additional information, json-hierarchical-driver=true indicates JSON driver will be used for marshalling, while json-hierarchical-driver=false indicates Jettison driver will be used for marshalling.
Resolved Issues
This release contains no resolved issues.
Upgrade Notes
No special procedure is required to upgrade to release 9.0.002.01.