question

Upvotes
Accepted
Adrian Lulea avatar image
5 ●0 ●0 ●2

Compatibility between Robust Foundation API RFA C++ 8.2.2 L1 and E1

Hello,

The last version of my software (Finastra Summit) has been built with RFA 8.2.2 L1.

We just noticed on your website that a kind of emergency version is available: RFA 8.2.2 E1.

We have the following questions:

  1. Do you confirm that we should use RFA 8.2.2 E1 instead of RFA 8.2.2 L1 in my next product patch?
  2. And is there any compatibility between RFA 8.2.2 L1 and RFA 8.2.2 E1 ?
    • i.e. if we have the product compiled against L1 but at runtime we put E1, will it work?


Kind regards,
Adrian L.

#technologyrfa
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvote
Accepted
Jirapongse avatar image
85k ●289 ●53 ●77

@Adrian Lulea

Thank you for reaching out to us.

RFA 8.2.2.E1 contains the fix of the following issue in RFA 8.2.2.L1.

--------
8.2.2.E1
--------
[RFA-882] - CaseId 13627839: The data encoding functions 'DataBuffer::setFromString' and
            'SingleWriteIterator::setEntryFromString' were modified to throw an InvalidUsageException
            instead of encoding default values or zero for the DataBuffer enumerations FloatEnum, DoubleEnum, RealEnum, Real32Enum, Real64Enum, DateEnum and TimeEnum when passed an invalid input that results in an overflow.

You can use 8.2.2.E1 to avoid this issue. Yes, 8.2.2.E1 is compatible with 8.2.2.L1. It is better to rebuild the application with 8.2.2.E1.

However, the latest version of RFA C++ is 8.2.4 which contains the following fixes and upgrades.

--------
8.2.4.L1
--------
[RFA-770] - Added support for Ubuntu Linux 20.04.6 LTS 64-bit.
[RFA-809] - CaseID: 12823229 - Added support for GCC 9.2.1 compiler on RHEL8 64-bit.
[RFA-283] - Fix for the issue: OrderBookDisplay application is crashing on exit for Debug libraries.
[RFA-768] - Removed the support for RHEL6 32-bit and 64-bit.
[RFA-820] - Removed the 32-bit support across Linux and Windows.


--------
8.2.3.L1
--------
[RFA-727] - Added support for Visual Studio 2022 64-bit.
[RFA-729] - CaseID: 11449757 - Log file is not generated when fileLoggerFilename contains full path to the executable.
[RFA-731] - Upgraded DACS to the version 7.8.0.L1.
[RFA-742] - Qualified RFA C++ 8.X on Windows Server 2019 Standard Edition 64-bit.
[RFA-769] - Removed support for CentOS 8.
[RFA-772] - Removed support for Visual Studio 2013 32-bit and 64-bit.
[RFA-783] - CaseID: 12605896 - Incorrect log message when RFA disconnects after the time interval specified against the configuration variable 'connectionPingTimeout'. 

--------
8.2.2.L1
--------
[RFA-522] - CaseID: 08274864 - Added Support for Visual Studio 2019 64-bit.
[RFA-553] - Added Support for Red Hat Enterprise Linux Advanced Server 8.0 64-bit.
[RFA-599] - Qualification of RFA C++ 8.X on Centos 8.0 64-bit.
[RFA-541] - Change in Library Name suffix from '150' to '141' for Visual Studio 2017 32-bit and 64-bit Libraries.
[RFA-634] - Removal of Support for Visual Studio 2012 32-bit and 64-bit.
[RFA-595] - CaseID: 09695303 - RFA to be able to handle mismatch field type without crashing.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Adrian Lulea avatar image Adrian Lulea
Thank you @Jirapongse for your response and clarification.


We intend to upgrade to 8.2.2.E1 version for now and will discuss internally if we'll upgrade to latest version in the near future or move to the new API.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.