- we have to deal with scripting implementations (groovy, beanshell, ruby)
- we need to deal with a shared context for plugins, like the guarded mojos
- we need to deal with plugins as core application logic which can also interact with plugins

* Along with this comes the testing strategies that make this work
* The repository model where plugins can be stored and cataloged

        return redirect(getClass());
    }

    // ===================================================================================
    //                                                                        Assist Logic
    //                                                                        ============
    /**
     * Creates a Role entity from form data.
     *
     * @param form the form containing the role data

        return redirect(getClass());
    }

    // ===================================================================================
    //                                                                        Assist Logic
    //                                                                        ============

    private static OptionalEntity<BoostDocumentRule> getEntity(final CreateForm form, final String username, final long currentTime) {

    @Test
    public void test_XContentBuilderCallback_withComplexLogic() {
        XContentBuilderCallback callback = (builder, params) -> {
            builder.startObject();

            // Add conditional logic
            if (params != null) {
                builder.field("hasParams", true);
            } else {
                builder.field("hasParams", false);
            }

import org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException;

/**
 * Use a regular expression search to find and resolve expressions within the POM.
 *
 * TODO Consolidate this logic with the PluginParameterExpressionEvaluator, minus deprecations/bans.
 */
@Deprecated
public abstract class AbstractStringBasedModelInterpolator extends AbstractLogEnabled
        implements ModelInterpolator, Initializable {

 * validate batching, chaining, signing, and NT_CREATE_ANDX extended handling.
 */
class AndXServerMessageBlockTest {

    /**
     * Test stub for AndXServerMessageBlock to control read/write logic.
     */
    static class DummyAndXBlock extends AndXServerMessageBlock {
        int paramWordsWritten = 0;
        int bytesWritten = 0;
        int paramWordsRead = 0;
        int bytesRead = 0;

    private static final String DEFAULT_DATE_FORMAT = "yyyyMMddHHmmss";

    private static String formatDate(Date date, boolean forSnapshotTimestamp) {
        // logic from metadata.mdo, class "Versioning"
        TimeZone timezone = TimeZone.getTimeZone("UTC");
        DateFormat fmt =

 */
public class RelatedContentHelper extends AbstractConfigHelper {

    /**
     * Default constructor for RelatedContentHelper.
     * The constructor does not perform any initialization logic as the actual
     * initialization is handled by the {@link #init()} method annotated with
     * {@code @PostConstruct}.
     */
    public RelatedContentHelper() {
        super();
    }

import org.opensearch.transport.client.Client;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.search.SearchHit;

/**
 * Helper class for scroll-based search operations in OpenSearch.
 * Centralizes scroll logic to reduce code duplication across settings and indexer classes.
 *
 * <p>This class provides methods to perform scroll-based searches with different processing patterns:
 * <ul>

# Utiliser des classes comme dépendances { #classes-as-dependencies }

Avant d'aller plus loin dans le système d'**Injection de dépendances**, mettons à niveau l'exemple précédent.

## Un `dict` de l'exemple précédent { #a-dict-from-the-previous-example }

Dans l'exemple précédent, nous renvoyions un `dict` depuis notre dépendance (« dependable ») :

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}