// Assert
        assertNotNull(msgs);
        assertTrue(msgs.length >= 3, "Expect at least the first 3 entries present");
        assertEquals("The operation completed successfully.", msgs[0]);
        assertEquals("Incorrect function.", msgs[1]);
        assertEquals("Incorrect function.", msgs[2]);
    }

    @Test

   *
   * This method returns false unless it is overridden by a subclass.
   *
   * ### Duplex Transmission
   *
   * With regular HTTP calls the request always completes sending before the response may begin
   * receiving. With duplex the request and response may be interleaved! That is, request body bytes
   * may be sent after response headers or body bytes have been received.
   *

    taskRunner.withLock {
      check(currentTask == TestThreadSerialTask)
      nanoTime = newTime
      yieldUntil(ResumePriority.AfterOtherTasks)
    }
  }

  /** Confirm all tasks have completed. Used by the test thread only. */
  fun assertNoMoreTasks() {
    taskRunner.assertLockNotHeld()

    taskRunner.withLock {
      assertThat(activeThreads).isEqualTo(0)
    }
  }

   * {@code null}; it may either return a non-null value or throw an exception.
   *
   * <p>No observable state associated with this cache is modified until loading completes.
   *
   * @throws ExecutionException if a checked exception was thrown while loading the value
   * @throws UncheckedExecutionException if an unchecked exception was thrown while loading the
   *     value

<img src="/img/tutorial/security/image12.png">

## Vérifier le nom d'utilisateur { #check-the-username }

Voici un exemple plus complet.

Utilisez une dépendance pour vérifier si le nom d'utilisateur et le mot de passe sont corrects.

        activityHelper.access(getUserBean(), requestPath, executeName);
        return super.hookBefore(runtime);
    }

    /**
     * Hook method called after action execution completes.
     * <p>
     * This method performs cleanup operations by calling the parent hook.
     * </p>
     *
     * @param runtime the action runtime context
     */
    @Override

        .isNotInstanceOf(ListenableFuture.class);
    ListenableFuture<String> listenable = listenInPoolThread(input);
    /*
     * This will occur before the waiting get() in the
     * listenInPoolThread-spawned thread completes:
     */
    RecordingRunnable earlyListener = new RecordingRunnable();
    listenable.addListener(earlyListener, directExecutor());

    input.allowGetToComplete.countDown();

              docker cp "${sql_file}" "${container_name}":"${sql_file}"
              docker exec -i ${TTY_FLAG} "${container_name}" bash -c "su - omm -c 'gsql -U omm -f ${sql_file}'"
              echo "Database initialization completed."
              break
            fi

            echo "Waiting for database to be ready... (attempt $((retry_count + 1))/$max_retries)"
            sleep 10
            ((++retry_count))
          done

Mais voici le point clé.

La partie sécurité et injection de dépendances est écrite une seule fois.

Et vous pouvez la rendre aussi complexe que vous le souhaitez. Et malgré tout, ne l'écrire qu'une seule fois, en un seul endroit. Avec toute la flexibilité.

Mais vous pouvez avoir des milliers d'endpoints (*chemins d'accès*) utilisant le même système de sécurité.

            }
            final LlmChatResponse response = client.chat(request);
            if (logger.isDebugEnabled()) {
                logger.debug("[LLM] LLM chat request completed. llmType={}", llmType);
            }
            return response;
        } catch (final LlmException e) {