Releases: SAP-archive/node-rfc
v2.0.2
v2.0.1
v2.0.0
Changes
- Connection Pool ported to C++
- Error handling improvements:
rfmPath
- New documentation content and format ported from
reStructuredText
tomarkdown
environment
object- node 6 and 8 support expired
- Connection attribute PartnerIPv6 added
- SAP NWRFC SDK post-installation fix for macOS removed
Cmake
version 3.17N-API
version 6N-API
version from package.json used in CMakeLists.txt, instead of separately (double) maintained onetslint
replaced byeslint
Breaking changes
-
Managed clients' can't open and close own connections any more. Instead of
open()
andclose()
,
managed clients use poolacquire()
andrelease()
methods. Delegation of these tasks to Pool,
ensures the connection handle stability during the Client instance lifecycle (less or not at all RFC_INVALID_HANDLE errors)
and more intuitive error messages, likeRFM call() over closed connection
instead of genericRFC_INVALID_HANDLE
error. -
After critical errors, the client connection handle is set to
NULL
, consequently setting thealive
property tofalse
.
Thealive
property now exposes theconnection handle != NULL
condition, thus always in sync. The automatic re-open should
assign the new connection handle to client, setting thealive
totrue
: see Closing connections. -
Client
reopen()
method removed -
Client
ping()
method result returned as a second callback parameter (callback pattern), error is the first -
Client getters:
status
andrunningRFCCalls
removedisAlive
replaced withalive
_connectionHandle
replaced withconnectionHandle
version
replaced with more genericenvironment
object, exposing:- os platform name, architecture, release
- node, napi, modules etc. versions (process.versions)
SAPNWRFC_HOME
andRFC_INI
environment variables
-
The ongoing RFC call is not any more protected from connection
close()
by direct client.
The direct clients should not call theclose()
method before the RFM call completed and
invoke()
orcall()
callback invoked. -
Error handling improvements:
- All error objects have now a
name
property, defining the error type - Error location path (rfm/parameter/field) attached to error objects, property
rfmPath
- All error objects have now a
v1.2.0
v1.1.0
Changes
- Safeguarding from closing the connection while RFC calls still running
- Number of running RFC calls exposed as client instance attribute
- Client logging
- Installation with NODE_ENV=production, fix #122
- Warnings when compiling for Windows IA32 platform, fix #131
- Ensure Bluebird Promises used instead of native Typescript, fix #134
- Pool reopen() fixed, returning now the Client instance, just like Pool open(), fix #135
- Pool max option removed, fix #136
- Unit tests refactoring
v1.0.6
Changes
- Connection Info update for PL6 e55783f #128
- Concurrent locking fix for ConnectionInfo() c5a443b #128
- Concurrent locking fix for invoke() and ping() 9cebb9a #128
- Security audit fix by dependencies update; fixes #129
- rstrip removed, always true
- Throughput monitoring: number of calls, bytes sent/received, application/total time; SAP NWRFC SDK >= 7.53 required
- UTCLONG ABAP datatype support; SAP NWRFC SDK >= 7.54 required
v1.0.5
v1.0.3
v1.0.2
v1.0.1
Features
- Min NodeJS version fixed in
package.json
, per NAPI version matrix - README: N-API badge added
- ABAP decimal floating point data types added: RFCTYPE_DECF16 and RFCTYPE_DECF34