3.1.9 - 2024-10-17

Dependency Updates

  • Update the commons-io:commons-io library to 2.17.0

3.1.8 - 2024-07-12

Internal updates only

3.1.7 - 2024-05-30

Internal updates only

3.1.6 - 2024-02-29

New Features

  • Support for running on Java 17 (tested with the Microsoft build of OpenJDK 17). Existing support for Java 11 is unchanged.

3.1.5 - 2024-02-12

Internal updates only

3.1.4 - 2023-11-13

Dependency Updates

  • Updated com.google.protobuf:protobuf-java to 3.19.6

  • Update org.apache.ivy:ivy to 2.5.2 (#987040)

3.1.3 - 2022-12-20

Note Release versions now have three components, not four.
This release requires Rhino 3.1 or later.

Dependencies

  • All open source libraries used by this resource adaptor have been updated to the latest available version, including:

    • com.google.protobuf:protobuf-java to 3.17.3. (The binary CDR format has not changed.)

3.0.0.0 - 2020-08-26

  • Java 11 is now supported. Earlier JDK versions are no longer supported.

2.3.0.1 - 2019-11-08

  • Fixed concurrency issue with CDR filenames when using %d and %D formatting options. (CDR-137)

  • Improved logging of errors from CDR command line tooling. (CDR-134)

2.3.0.0 - 2016-07-15

New Features

  • Added support for multiple independently configured "streams" within a single resource adaptor entity. Services select which stream to write a record to. (CDR-28)

  • Added support for active reconfiguration of resource adaptor entities. (CDR-45)

  • Added an MXBean that allows the stream configuration state to be inspected. (CDR-48)

  • Added an extensible tool to simplify development of custom business logic for processing binary CDR files. (CDR-39)

  • Added support for extension fields to the binary CDR processing tools. (CDR-19)

2.2.0.0 - 2011-11-10

  • Added binary CDR file support. (CDR-15)

  • Added support for CDR objects which have type com.google.protobuf.Message or Object. (CDR-8)

  • Added '--formatted' option to the ListCdrs tool to produce more easily readable output. (CDR-25)

  • Added new config property "WriteWait". When set to "False", the resource adaptor will not wait for the CDR to be written to the file before reporting success to the calling SBB. This can be used to reduce latency in writing CDRs but means that queued CDRs will be lost in the event of a write error or node failure. When set to "True", the resource adaptor will only report success to the caller once the CDR has been written to the file. The default is "True", which gives the same behaviour as previous versions. (CDR-24)

  • Fixed a NullPointerException that occurred when a text CDR file was closed if the resource adaptor was configured not to output a footer line to the file. (CDR-20)

  • Updated configuration default values in documentation. (CDR-21)