*/
    public static QueryFieldConfig getQueryFieldConfig() {
        return getComponent(QUERY_FIELD_CONFIG);
    }

    /**
     * Gets the query processor component.
     * @return The query processor.
     */
    public static QueryProcessor getQueryProcessor() {
        return getComponent(QUERY_PROCESSOR);
    }

    /**
     * Gets the label type helper component.

/**
 * Helper class for managing Fess plugins and artifacts.
 * This class provides functionality to discover, install, and manage various types of plugins
 * including data stores, themes, ingest processors, scripts, web applications, thumbnails, and crawlers.
 */
public class PluginHelper {
    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(PluginHelper.class);

    /**

 *
 * <ul>
 *   <li>An annotation named just "Suppress" might someday be treated by a non-Android tool as a
 *       suppression. This would follow the precedent of many of our annotation processors, which
 *       look for any annotation named, e.g., "GwtIncompatible," regardless of package.
 *   <li>An annotation named just "Suppress" might suggest to users that the test is suppressed

Mas tenha em mente que, como tudo é manipulado na memória, em uma única lista, ele só funcionará enquanto o processo estiver em execução e só funcionará com um único processo.

        assertNull(result);
    }

    // Test convertBooleanQuery with null queryBuilder from processor
    public void test_convertBooleanQuery_withNullQueryBuilder() {
        // Create processor that returns null
        QueryProcessor nullProcessor = new QueryProcessor() {
            @Override

# Helper function to copy a srcjar after moving any source files
# directly under the root to the "maven-style" src/main/java layout
#
# Source files generated by annotation processors appear directly
# under the root of srcjars jars created by bazel, rather than under
# the maven-style src/main/java subdirectory.
#
# Bazel manages annotation generated source as follows: First, it

   * @param callback the LineProcessor to use to handle the lines
   * @return the output of processing the lines
   * @throws IOException if an I/O error occurs
   */
  @CanIgnoreReturnValue // some processors won't return a useful result
  @ParametricNullness
  public static <T extends @Nullable Object> T readLines(
      URL url, Charset charset, LineProcessor<T> callback) throws IOException {

import org.codelibs.fess.crawler.exception.ChildUrlsException;
import org.codelibs.fess.crawler.exception.CrawlerSystemException;
import org.codelibs.fess.crawler.processor.ResponseProcessor;
import org.codelibs.fess.crawler.processor.impl.DefaultResponseProcessor;
import org.codelibs.fess.crawler.rule.Rule;
import org.codelibs.fess.crawler.rule.RuleManager;
import org.codelibs.fess.crawler.serializer.DataSerializer;

E também depois que a `response` é gerada, antes de retorná-la.

Por exemplo, você pode adicionar um cabeçalho personalizado `X-Process-Time` contendo o tempo em segundos que levou para processar a solicitação e gerar uma resposta:

{* ../../docs_src/middleware/tutorial001.py hl[10,12:13] *}

## Outros middlewares

    }

    public void test_processUrl() {
        assertEquals(0, urlFilter.cachedIncludeSet.size());
        assertEquals(0, urlFilter.cachedExcludeSet.size());

        urlFilter.processUrl("http://example.com/");

        assertEquals(0, urlFilter.cachedIncludeSet.size());
        assertEquals(0, urlFilter.cachedExcludeSet.size());
    }