Releases: finos/symphony-bdk-java
Releases · finos/symphony-bdk-java
symphony-api-client-java-1.0.47
- Added MessageUtils helper class for transforming stream ids and sanitising untrusted text content to be sent as part of outgoing messages
- Added super() call in AuthenticationException so calling getRootException is not necessary
symphony-api-client-java-1.0.46
- Standardised all API calls to use try-with-resources to prevent potential non-release of any response objects
- Updated jackson-databind and slf4j versions
symphony-api-client-java-1.0.45
- Replaced /sessioninfo call during initialisation with parsed username and id from sessionToken
- Added persistence and re-use of datafeed id to prevent missed messages during bot outages
- These changes along with parallel RSA auth introduced in 1.0.43 reduces bot startup time by over 70%
symphony-api-client-java-1.0.44
- Removed parallel auth from certificate-based auth
- Minor library upgrades
symphony-api-client-java-1.0.43
- Key manager and session authentication now run in parallel
- Added addTextField without min/max lengths to Elements FormBuilder
- Upgraded jackson-databind to 2.9.10
- Fixed bug: proxy not working together with connectionTimeout settings
symphony-api-client-java-1.0.41
- Added exponential backoff for handling connection failures
- Added checkstyle rules and validation
symphony-api-client-java-1.0.40
- Removed ApacheConnectorProvider causing http headers warning
- Added graceful error for handling connection timeout instead of printing stack trace
- Added <br> and <div> methods to FormBuilder
- Added JAXB API dependency to be natively compatible with JDK >8
symphony-api-client-java-1.0.39
- Bugfix: connection timeout settings not applied when load balancer configuration is used
symphony-api-client-java-1.0.38
- Support for Symphony Elements
- Added default connection timeout of 35s to prevent hung data feed reads
symphony-api-client-java-1.0.37
- Added connection timeout support and refactored proxy configuration
- Updated jackson-databind to address CVE-2019-14379 and CVE-2019-14439