///

## Combining information { #combining-information }

You can also combine response information from multiple places, including the `response_model`, `status_code`, and `responses` parameters.

You can declare a `response_model`, using the default status code `200` (or a custom one if you need), and then declare additional information for that same response in `responses`, directly in the OpenAPI schema.

    /**
     * Document URL patterns to exclude from search index.
     */
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String excludedDocUrls;

    /**
     * Additional configuration parameters for the crawler.
     */
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String configParameter;

    /**
     * The maximum crawling depth from the starting URLs.
     */

/**
 * Entity class representing facet configuration information for search results.
 * This class holds configuration settings for faceted search including field facets,
 * query facets, and various parameters that control facet behavior.
 */
public class FacetInfo {
    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(FacetInfo.class);

    /**
     * Retrieves crawling info logs with pagination support.
     *
     * @param body the search body containing pagination and filter parameters
     * @return JSON response containing list of crawling info logs
     */
    // GET /api/admin/crawlinginfo/logs
    // PUT /api/admin/crawlinginfo/logs
    @Execute

import jcifs.internal.util.SMBUtil;

/**
 * SMB Direct Negotiate Request message.
 *
 * As per MS-SMBD 2.2.1 - SMB_DIRECT_NEGOTIATE_REQUEST
 * This message is sent to negotiate SMB Direct protocol parameters.
 */
public class SmbDirectNegotiateRequest {

    // Protocol constants
    /** Minimum supported SMB Direct protocol version (1.0) */
    public static final int MIN_VERSION = 0x0100; // SMB Direct 1.0

        SYSTEM_PROPERTIES,
        /**
         * Maven user properties. These are properties that users configure through various means such as
         * maven-user.properties files, maven.config files, command line parameters (-D flags), settings.xml,
         * or environment variables. They are evaluated during the build process and represent the primary
         * way for users to customize Maven's behavior at runtime.
         */

    /** The facet response containing aggregated facet information for the search results. */
    protected final FacetResponse facetResponse;

    /**
     * Constructs a new SearchResult with the specified parameters.
     *
     * @param documentList The list of documents returned by the search
     * @param allRecordCount The total number of matching records
     * @param allRecordCountRelation The relation type for the record count

            result.setCreatedTime(DfTypeUtil.toLong(source.get("createdTime")));
            result.setHostname(DfTypeUtil.toString(source.get("hostname")));
            result.setParameters(DfTypeUtil.toString(source.get("parameters")));
            result.setPassword(DfTypeUtil.toString(source.get("password")));
            result.setPort(DfTypeUtil.toInteger(source.get("port")));

  export -p | grep TFCI

  # Load those stored pre-existing TFCI_ vars, if any
  if [[ -s "$FROM_ENV" ]]; then
    echo '==TFCI==: NOTE: Loading the following env parameters, which were'
    echo 'already set in the shell environment. If you want to disable this'
    echo 'behavior, create a new shell.'
    cat "$FROM_ENV"
    source "$FROM_ENV"
    rm "$FROM_ENV"
  fi
  set +u
fi

     */
    public DocumentHelper() {
        // Default constructor
    }

    /**
     * Initializes the document helper after construction.
     * Sets up the TikaExtractor with configuration parameters for text processing.
     */
    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {
            logger.debug("Initialize {}", this.getClass().getSimpleName());
        }
        try {