@BeforeEach
    @Override
    public void setUp() throws Exception {
        super.setUp();
        projectArtifact = createLocalArtifact("project", "3.0");
    }

    @Override
    protected String component() {
        return "resolver";
    }

    @Test
    void testMNG4738() throws Exception {
        Artifact g = createLocalArtifact("g", "1.0");
        createLocalArtifact("h", "1.0");

    }

    // ===================================================================================
    //                                                                           Component
    //                                                                           =========
    protected MessageManager getMessageManager() {
        return ContainerUtil.getComponent(MessageManager.class);
    }

    }

    /**
     * Initializes the facet query view with default file type queries.
     * This method is called after dependency injection to set up file type facets
     * and register all queries with the FacetInfo component.
     */
    @PostConstruct
    public void init() {
        final String filetypeField = ComponentUtil.getFessConfig().getIndexFieldFiletype();
        final Collection<String> values = queryMap.values();

Alles als wiederverwendbare Tools und Komponenten gebaut, die einfach in ihre Systeme, Datenspeicher, relationalen und nicht-relationalen Datenbanken, usw., integriert werden können.

### Einbringen von Abhängigkeiten (Dependency Injection)

Dieses Beispiel ist jedoch immer noch gültig und zeigt, wie mit den internen Komponenten interagiert wird.

///

Wir können denselben Ansatz auch verwenden, um in einem Exceptionhandler auf den Requestbody zuzugreifen.

/*!
 * Timepicker Component for Twitter Bootstrap
 *
 * Copyright 2013 Joris de Wit
 *
 * Contributors https://github.com/jdewit/bootstrap-timepicker/graphs/contributors
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.

 * the parsing of the response body.
 * </p>
 */
public class SitemapsResponseProcessor implements ResponseProcessor {
    /** The crawler container for component lookup. */
    @Resource
    protected CrawlerContainer crawlerContainer;

    /**
     * Creates a new SitemapsResponseProcessor instance.
     */
    public SitemapsResponseProcessor() {
        super();

<component name="InspectionProjectProfileManager">
  <profile version="1.0">
    <option name="myName" value="Gradle" />
    <inspection_tool class="21f28a86-2ba8-3048-9ce1-b6f10d4d4a12" enabled="true" level="WEAK WARNING" enabled_by_default="true" editorAttributes="INFO_ATTRIBUTES" />
    <inspection_tool class="73cd39e8-e54e-3a38-ad1b-b883fff4b1eb" enabled="true" level="WEAK WARNING" enabled_by_default="true" editorAttributes="INFO_ATTRIBUTES" />

     *
     * @return the logger instance
     */
    Logger getLogger();

    /**
     * Extracts the host name from a URL string.
     * Removes protocol and path components to return just the hostname.
     *
     * @param u the URL string to extract host from
     * @return the host name, or empty string if URL is blank, or unknown hostname if parsing fails
     */

# How to configure Prometheus AlertManager

Alerting with prometheus is two step process. First we setup alerts in Prometheus server and then we need to send alerts to the AlertManager.