Versions Compared

Old Version 22

changes.mady.by.user Rea Ben Yossef

Saved on

compared with

New Version Current

changes.mady.by.user Rea Ben Yossef

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

January 20, 2021 (v4.5.15)

Improvements

  • Users can now toggle between trimming string fields (default behavior) and not-trimming (new behavior) on the SDK level

December 1, 2020 (v4.5.14)

Improvements

  • New Legacy type to support Mixed input English (in double byte representation) and Korean/Japanese

...

November 29, 2020 (v4.5.13)

Improvements

  • SDK Projects can now be defined to support BIDI text on the project level . Specific fields can be defined to override project level behavior. This improves Runtime handling of BIDI text to/from the legacy system

November 15, 2020 (v4.5.12)

Improvements

...

October 20, 2020 (v4.5.11)

Improvements

  • The Mainframe CICS TG connector now supports transmitting data in containers, rather than only using the COMMAREA

  • The delay on reading the input stream from the socket was successfully reduced to 50ms

  • The following 3rd party application versions were updated

    • Vertx 3.9.2 → 3.9.3

    • Spring Boot 2.3.2 → 2.3.4 (https://spring.io/blog/2020/08/13/spring-boot-2-3-3-available-now)

    • Spring Cloud Hoxton.SR5 → Hoxton.SR8

    • spring-security-oauth2-autoconfigure 2.3.1 → 2.3.3 → 2.3.4

    • commons-io 2.6 → 2.8.0

    • kotlin Logging 1.7.9 → 1.11.3 → 1.12.0

    • swagger-parser 1.0.50 → 1.0.51

    • swagger-parser-v3 2.0.18 → 2.0.21 → 2.0.22

    • swagger 1.6.0 → 1.6.2

    • bouncycastle 1.65 → 1.66

    • commons-net 3.6 → 3.7 → 3.7.1

    • commons-text 1.8 → 1.9

    • flatten-maven-plugin 1.0.0 → 1.2.5

    • maven-surefire-plugin 3.0.0-M4 → 3.0.0-M5

    • maven-failsafe-plugin 3.0.0-M4 → 3.0.0-M5

    • exec-maven-plugin 1.6.0 → 3.0.0

    • frontend-maven-plugin 1.9.1 → 1.10.0 ->1.10.3

    • fabric8-maven-plugin 4.4.0 → 4.4.1

    • maven-site-plugin 3.9.0 → 3.9.1

    • io.grpc 1.27.2 → 1.32.1

    • grpc-spring-boot-starter 3.5.3 → 3.5.7 → 4.0.0

    • protobuf-java 3.11.4 → 3.13.0

    • jprotobuf 2.4.1 → 2.4.4

    • protoc 3.11.4 → 3.13.0

    • protoc-gen-grpc-java 1.27.2 → 1.32.1

    • aws-lambda 1.2.0 → 1.2.1

    • glassfish-jaxb 2.3.2 → 2.3.3

    • jaxws-rt 2.3.2 → 2.3.3

    • cxf-spring-boot-starter-jaxws 3.3.6 → 3.4.0

    • powermock 2.0.5 → 2.0.7

    • guava 28.2-jre → 29.0-jre

    • Removed:
      com.spotify:docker-maven-plugin (we are using the active dockerfile-maven-plugin)

  • ‘add-files’ now supports handling Freemarker templates from external folders.

...

  • Templating a Project has been simplified, allowing implementers to set dynamic parameters which will then be incorporated into the New SDK/API Project wizards and to the Entity/Service Generation wizards. This reduces the need to create a template for each and every variation from the original template.

  • Log Level TRACE now displays both the Hex buffer value and the Java value mapped to/from entity fields in requests and responses.

Improvements

  • The COBOL parser now supports Dynamic lists that are explicitly defined in COBOL (DEPENDS ON clause)

  • Encryption key can be now set in a separate file rather than in the YAML configuration. This is useful when moving projects between environments.

  • Trust-store configuration has been updated to allow REST SDKs to call APIs using Secure SSL

  • An output offset can now be configured in the IMS Connector YAML file. This will instruct the Runtime to read the buffer from the defined offset

  • Backend Timeouts can now be configured in the YAML file of CICS projects

  • Fields to be excluded can now be defined in the Testing Framework. This will allow variable fields (such as Age) to be excluded from a test

...

  • IDE:

    • Dynamic List attributes can now be set in the Entity/Part editor , under “Dynamic Attributes”

    • The .ol-config.yml file can now be used in a template and will not be overridden when a template is used.

    • AS/400 Connector - Default Service ports can now be overridden

Improvements

  • Connectors:

    • File Connector SDK Project:

      • A byte array can now be returned instead of an actual file

      • The Carriage Return type and encoding to be applied to the output file can now be set in the Create SDK Project wizard

      • The file name generated by the SDK can be overridden by entering a specific name on the request

    • Oracle SP - %ROWTYPE and %TYPE are now supported

    • PL1 signed number handling was improved in Runtime and parsing

...

  • PL1 parsing - parts are no longer automatically generated without reason (a part with a single simple field for example)

July 14, 2020 (v4.5.8)

Improvements

  • Runtime has been improved to handle IMS errors and reflect them rather than just throwing a generic error

  • PL1 parsing has been enhanced to enable automatically assigning field direction with the Field Name pattern. For example: fields that start with “in_” should be assigned the direction of INPUT and fields that start with “out_” should be assigned the direction of OUTPUT.

  • File connector - namespace added to the root element - You can now define the desired namespace that should be added to the final XML file directly on the entity.

  • MQ connector - The MQ Connector now supports the ability to browse message by certain value instead of correlation id - MQ Browse Option

...

  • File Connector - OpenLegacy Connectors

  • Users can now generate a JUnit test based on selected Entity (SDK) or Service (API) - Generating JUnit Tests

  • AS/400 program parameters can now be sent by Value or by Reference. Default behavior has been changed to be By Reference.

Improvements

  • Angular support for all HTTP method types, including GET, POST, PUT, DELETE and PATCH

  • Added Padding (advanced) attribute to String type field. Users can now define the Padding Type and character to use when padding String fields. RPC Attributes - Fields Tab, Screen Attributes - Fields Tab

  • Users can now configure the User Exit Message identifier on the request and determine which IMS Connect user message exit is to be used for this interaction after the complete input or output message has been received by IMS Connect.

...

  • When mapping an expression of type X to a field of type Y, the Conversion suggestion list will show only relevant converters (out-of-the-box converters and custom converters that convert from type X to type Y). If only one converter exists, it will be auto-selected as default, otherwise the first converter from the list will be auto selected.

Improvements

  • Added ability to customize the REST HTTP request header before sending it by creating a REST mechanism similar to CicsHttpRequestCustomizer.

...

No new features were added

Improvements

  1. The PATCH HTTP Verb option was added to the Input wrapper drop down in the Service’s Methods tab - API Editor - Methods Tab

  2. Service Editor Mapping Tab : Improved mapping capabilities. You can now turn Integers and BigDecimals to strings ,map String Constants to business entities fields and map list fields with ease.

...

No new features were added

Improvements

  1. In alignment with Oracle’s Support policy for Java, Java 8 is no longer supported. Our Windows installation will include the latest version of OpenJDK 11. Linux and Mac installations require you to install Java 11 independently. The Code itself remains Java 8 compatible in this release.

  2. Oracle JDBC driver has been upgraded to ojdbc8 latest version, in order to be compatible with both Oracle 19c and JDK8 which we will still be supporting in this version for backward compatibility reasons.

  3. Upgrade Spring Cloud to Hoxton.SR3

  4. Upgrade kotlin to 1.3.70 -

  5. Change jaxb-xml and jaxb-core to glassfish. Therefore, we will have jaxb-api + glassfish jaxb-runtime (we keep jaxb-api and replace jaxb-core + jaxb-impl with glassfish jaxb-runtime). Dependencies were changed to point to Glassfish. This means that users do not need to manually add JAXB jars

  6. List fields can be mapped between Entity and Outputs. How To Map List Fields1

...

No new features were added

Improvements

  • The Microservice environment was aligned with v 4.5.x

  • Added support to use Date pattern for the primitive Date fields inside the Input/Output tab for RESTful API projects.
    When generating an API (using the dialog “Generate API from SDK”), the user can select a Date field from the SDK entity as input or output. The pattern that was specified for this field in the SDK entity will be used for the service input/output field (for example the pattern from the @RpcDateField annotation).

...

  • A new Testing Framework was introduced to automate unit testing.

  • A new Graphtalk connector was introduced. This connector allows the OpenLegacy platform to generate Java entities from Graphtalk XML files.

Improvements

  • Additional Run Time support for Cpy files including Saved Words (ZERO, SPACE, etc.)

    • Additional support in PL/I:

    • PL/I Design Time and Run Time support for all input and output Datatypes

    • PL/I Design Time and Run Time support for DBCS type fields - these are double byte characters for Japanese language

    • PL/I Parser Design Time Support to Generate Entities with Include Directives in their sources

  • CICS Design Time and Run Time support for DBCS type fields - these are double byte characters for Japanese language

  • A Single Sign-On (SSO) connection to SAP can be set up using the SAP Logon ticket

  • The License Process was updated in line with OpenLegacy’s Licensing Policy

  • Spring Boot was upgraded to Spring Boot 2. Please note that Spring Boot 2 requires Java 8 as the minimal version

  • JDK was upgraded to OpenJDK 11.

  • Best Practices for secure coding were updated and reviews

  • Product security improved by using Snyk.io to find & fix vulnerable dependencies with open source code

  • The infrastructure of the OpenLegacy Core engine was improved to provide performance improvements in Run Time

  • Connection Pool Max Size can be configured when using MF Connector

  • Entity definitions were refactored (see details)

  • Decreased use of reflections across the product to improve performance and reduce the product footprint. This is part of a major initiative to improve Open:Legacy performance; additional improvements will follow.

...