The MSPro Boomi Collection
About
ScriptEase For Boomi
ScriptEase For Boomi
  • ScriptEase
    • ScriptEase Development Environment
    • What AI says!
      • The limits of AI ...
  • Software Installation
    • Install a local Atom
  • Project Setup
    • IntelliJ Configuration
    • Verify Project Setup
  • Concepts
    • Use Test Data
  • Examples
    • 1 - Debug an existing process script
    • 9 - Aggregate Prices Example
  • Test Contexts
    • The Process Call Chain
  • Download
  • 💤Appendix
    • Script Templates
    • Java thoughts and recommendations
      • Chose newer JVM for local development
    • Boomi documentation and links
    • Initialize IntelliJ Templates
    • Script Contexts
  • Troubleshoot
    • Java the weed
    • ClassNotFoundException - GroovyStarter
    • Invalid VCS root mapping
    • An illegal reflective access operation has occurred
    • UnauthorizedAccess Error
  • Licensing
    • License Activation
    • Privacy Policy
Powered by GitBook
On this page
  1. Appendix

Java thoughts and recommendations

Last updated 6 months ago

JDK, SDK, JRE, 11, 17, 23, ... Java confuses me because my impression is: patchwork.

Groovy Scripts are pre-compiled into byte-code to run on the Java Virtual Machine (JVM).

  • Groovy is not interpreted during run-time. It is pre-compiled before it runs, and the resulting byte-code is executed on a JVM.

    • The Groovy compiler groovc is part of the Groovy package.

    • Groovy needs a JVM as its execution platform.

  • When the script runs on the Atom, the Atom's JVM runs the script.

  • When the script runs a the local machine, the determines the JVM.

Until today (2024-11-19) I recommended to use the Atom JVM as the Project SDK so that a script is executed with the same Java Virtual Machine Version as when it runs on the Atom.

However, when you get unrecognisable warnings during development it is probably because of the (legacy) Java 11.

💤
Project SDK
(Local) Atom Startup Properties