* crawling operations through the administrative interface wizard workflow.
 * It serves as a data transfer object between the web layer and the crawling
 * service components.
 */
public class StartCrawlingForm {

    /**
     * Default constructor.
     */
    public StartCrawlingForm() {
        // Default constructor
    }

    }

    /**
     * Gets the list of page numbers to display in the pagination component.
     *
     * @return the list of page numbers, or null if not set
     */
    public List<Integer> getPageNumberList() {
        return pageNumberList;
    }

    /**
     * Sets the list of page numbers to display in the pagination component.
     *
     * @param pageNumberList the list of page numbers to set
     */

/**
 * Marker interface to indicate services that can be provided by plugins and extensions.
 * <p>
 * This interface serves as the base for all Service Provider Interface (SPI) components in Maven.
 * Classes implementing this interface can be discovered and loaded by Maven through the
 * Java ServiceLoader mechanism, allowing plugins and extensions to contribute functionality
 * to the Maven build process.

     * in the data store plugin directory and extracts component class names.
     *
     * <p>The method uses secure XML parsing features to prevent XXE attacks and
     * other XML-based vulnerabilities. Component class names are extracted from
     * the 'class' attribute of 'component' elements in the XML files.</p>
     *

    void testWithNullValues() {
        // Test null path
        testImplementation.setPath(null);
        assertNull(testImplementation.getPath());

        // Test null UNC path components
        testImplementation.setFullUNCPath(null, null, null);
        assertNull(testImplementation.getDomain());
        assertNull(testImplementation.getServer());
        assertNull(testImplementation.getFullUNCPath());

At first, it didn't have an automatic API documentation web UI, but I knew I could add Swagger UI to it.

It had a dependency injection system. It required pre-registration of components, as other tools discussed above. But still, it was a great feature.

    assertThat(url.toString()).isEqualTo("http://host/?a=!$(),/:;?@[]\\^`{|}~")
    assertThat(url.queryParameter("a")).isEqualTo("!$(),/:;?@[]\\^`{|}~")
  }

  /**
   * When callers parse a URL with query components that aren't encoded, we shouldn't convert them
   * into a canonical form because doing so could be semantically different.
   */
  @Test
  fun queryCharactersNotReencodedWhenParsed() {

import org.opensearch.transport.client.Client;

/**
 * OpenSearch client implementation specifically for crawler operations.
 * Extends FesenClient to provide search engine connectivity for the crawler components.
 */
public class CrawlerEngineClient extends FesenClient {

    /**
     * Creates a new instance of CrawlerEngineClient.
     */
    public CrawlerEngineClient() {
        super();
    }

import org.apache.maven.api.annotations.Consumer;
import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.di.Named;

/**
 * Component able to contribute to Maven session user properties. This SPI component is invoked
 * very early, while there is no session created yet.
 *
 * @since 4.0.0
 */
@Experimental
@Consumer
@Named
public interface PropertyContributor extends SpiService {

/**
 * Denotes that a bean should be created as a singleton instance.
 * <p>
 * Singleton-scoped beans are instantiated once and reused throughout the entire
 * Maven execution. This scope should be used for stateless services or components
 * that can be safely shared across the entire build process.
 * <p>
 * Example usage:
 * <pre>
 * {@literal @}Singleton
 * public class GlobalConfiguration {
 *     // Implementation
 * }
 * </pre>
 *