JavaScriptCaller Transformer Deprecation

Liz Sanderson
Liz Sanderson
  • Updated

FME Version

  • FME 2018.x

Introduction

Safe Software is taking steps to deprecate the JavaScriptCaller transformer. It will be phased out in a series of stages. This article explains the reasoning and timeline for this deprecation.

Justification

The JavaScriptCaller has a number of problems that currently reduce its usefulness.

Some of these issues are:

  • The transformer does not work in some Server contexts.
  • The transformer requires a major upgrade to continue to work on the macOS platform.
  • The transformer requires Python 2.7 to build, which is itself being deprecated.

Resolving these issues and keeping the maintenance up-to-date cannot, sadly, be justified by its current use statistics.

Timeline

The intended deprecation timeline is as follows:

FME2018.x

In FME2018 (FME2018.1.1, build 18579 onwards)...

  • A workspace using this transformer causes a warning message to occur in the log:
"The JavaScriptCaller transformer will be removed in FME 2020. Please consider migrating to a PythonCaller or other solution to avoid future inconvenience"

FME2019

In FME2019...

  • The transformer will be completely removed from macOS installations.
    • Once the transformer is completely removed from a platform it will not be possible to add a new instance, and a workspace containing the transformer will not operate.
  • The transformer will remain operable in Windows and Linux installations, but will be hidden from the Workbench interface so that new instances cannot be added.
  • No faults will be fixed or enhancements made to the transformer.

FME2020+

In FME2020 and beyond...

  • The transformer will be completely removed from all platforms.
    • Once the transformer is completely removed it will not be possible to add a new instance, and a workspace containing the transformer will not operate.

Alternatives

The FME support team is available to help with any questions about this deprecation, involving alternative solutions to current JavaScriptCaller use.

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.