Support programatically customizing SeContainer

[mpkorstanje]

The CdiJakartaFactory creates a container using the SeContainerInitializer.

    private SeContainer container;

    @Override
    public void start() {
        if (container == null) {
            SeContainerInitializer initializer = SeContainerInitializer.newInstance();
            initializer.addExtensions(this);
            container = initializer.initialize();
        }
    }

This starts a CDI application without any customizations. This is less then ideal when testing as certain parts may need to be stubbed out. As solution to this would be similar to #2432 and #1911 where a Backend implementation is used to scan for classes that implement a SeContainerInitializerProvider. The CdiJakartaFactory can then use this provider to create a cutomized initializer.

So as a quick sketch:

package com.example.stepdefinitions;


class MySeContainerInitializerProvider implements ContainerInitializerProvider {

    public SeContainer get() {
           // Provide/ container here
    }
}

Alternatively, or additionally, instead of asking the user to provide the entire container, we can ask the user to customize the existing container.

package com.example.stepdefinitions;


class MySeContainerCustomizer implements SeContainerCustomizer {

    public void customize(SeContainerInitializer sci) {
       // do customizations here    
    }
}

I don't know much about CDI so I think this is best left to the best judgement of people who use CDI.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two months if no further activity occurs.