errors.app.db.already.updated = Es wurde möglicherweise von einem anderen Prozess aktualisiert. Bitte versuchen Sie den Vorgang erneut.
errors.app.db.already.exists = Die Daten sind bereits vorhanden. Bitte versuchen Sie den Vorgang erneut.
errors.app.double.submit.request = Es wurde möglicherweise vor dieser Anfrage verarbeitet. Bitte versuchen Sie den Vorgang erneut.

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

     */
    public void shutdown() {
        shutdownListener.onShutdown();
    }

    /**
     * Adds a shutdown listener to be notified when the executor is shutting down.
     *
     * @param listener the shutdown listener to add
     */
    public void addShutdownListener(final ShutdownListener listener) {
        shutdownListener = listener;
    }

    /**

3. If the daemon is not able to run the request, for example it is already running a request or is shutting down, it rejects the request. The client starts again.
4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.

        val rootDirFiles = projectDir.resolve("build").walk().toList()

        archiveFileNames.forEach { fileName ->
            assertTrue(rootDirFiles.any { it.name == fileName }, "File $fileName does not exist")
        }
    }

    private
    fun assertLeftoverFilesCleanedUpEventually(vararg leftoverFiles: String) {
        leftoverFiles.forEach {

constraints.NotNull.message = {item} is required.
constraints.Null.message = {item} must be null.
constraints.Past.message = {item} must be a past value.
constraints.Pattern.message = {item} does not match "{regexp}".
constraints.Size.message = The size of {item} must be between {min} and {max}.
# ----------------------------------------------------------
# Hibernate Validator
# -------------------

constraints.NotNull.message = {item} is required.
constraints.Null.message = {item} must be null.
constraints.Past.message = {item} must be a past value.
constraints.Pattern.message = {item} does not match "{regexp}".
constraints.Size.message = The size of {item} must be between {min} and {max}.
# ----------------------------------------------------------
# Hibernate Validator
# -------------------

    }

    @Test
    public void test_escapeValue_noSpecialChars() {
        assertEquals("admin", LdapUtil.escapeValue("admin"));
        assertEquals("john.doe", LdapUtil.escapeValue("john.doe"));
        assertEquals("user123", LdapUtil.escapeValue("user123"));
        assertEquals("Test User", LdapUtil.escapeValue("Test User"));
    }

    @Test
    public void test_escapeValue_backslash() {

            try {
                fileConfig = fileConfigService.getFileConfig(getFileConfigId()).get();
            } catch (final Exception e) {
                logger.warn("File Config {} does not exist.", getFileConfigId(), e);
            }
        }
        return fileConfig;
    }

    @Override
    public String toString() {

With Java serialization, even minor changes to a class (like adding a field) can break compatibility.

- **Cross-Language Compatibility:**
Java serialization is inherently Java-centric and does not support cross-language scenarios well.

- **Type Safety:**
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.

## Decision

We do not use Java serialization.