# Java thoughts and recommendations

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 [*Project SDK*](/boomi-scriptease/setup-a-customer-project-a5e8a967b06b4f9d9123b55f72e07145/intellij-configuration.md#configure-sdk) determines the JVM.

{% hint style="info" %}
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.
{% endhint %}

<figure><img src="/files/4EeAWIrQyFBpziWF5lsd" alt=""><figcaption><p>(Local) Atom Startup Properties</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://boomi.markusschmidt.pro/boomi-scriptease/knowlede-base/java-jdk.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.