}

    /**
     * @throws Exception
     */
    @Test
    public void testExcludes() throws Exception {
        final CopyOptions option = new CopyOptions();
        assertThat(option.exclude(BeanNames.hoge()), is(sameInstance(option)));
        assertThat(option.excludePropertyNames.size(), is(1));
        assertThat(option.excludePropertyNames.get(0), is("hoge"));
    }

    /**
     * @throws Exception

/// warning

If you do this, you have to make sure each one of your *path operation functions* has a unique name.

Even if they are in different modules (Python files).

///

## Exclude from OpenAPI { #exclude-from-openapi }

To exclude a *path operation* from the generated OpenAPI schema (and thus, from the automatic documentation systems), use the parameter `include_in_schema` and set it to `False`:

import jakarta.validation.constraints.Size;

/**
 * Form class for creating new stopwords dictionary entries.
 * This form handles the creation of stopwords that should be
 * excluded from search indexing and analysis.
 *
 */
public class CreateForm {

    /**
     * Creates a new CreateForm instance.
     */
    public CreateForm() {
    }

    /**
     * URL patterns to exclude during crawling.
     */
    @CustomSize(maxKey = "form.admin.max.input.size")
    public String excludedUrls;

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

    /**
     * Document URL patterns to exclude from search index.
     */

     * Retrieves a list of URLs that should be excluded from crawling based on failure counts.
     * URLs are excluded if they have failed more than the configured failure count threshold.
     * URLs can also be filtered by failure type using a regular expression pattern.
     *
     * @param configId the configuration ID to get excluded URLs for
     * @return a list of URLs that should be excluded from crawling, or an empty list if none
     */

        #
        #; objectTypeTargetList = list:{TABLE ; VIEW}

        # o tableExceptList: (NotRequired - Default list:{})
        #  If you want to exclude some tables in generating target,
        #  you should specify the list of excepted table hints.
        #    e.g. list:{PRODUCT_STATUS ; prefix:TMP_}
        #  This is only for the main schema. Additional schemas are unconcerned.

    /**
     *
     */
    public String xyz_value = "xyz";

    /**
     *
     */
    public String other = "other";

    /**
     *
     */
    public String abc_exclude = "exclude";

    /**
     *
     */
    public String ab = "ab";

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

     * @return HTML response for the search results
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse search(final SearchForm form) {
        copyBeanToBean(form, labelTypePager, op -> op.exclude(Constants.PAGER_CONVERSION_RULE));
        return asHtml(path_AdminLabeltype_AdminLabeltypeJsp).renderWith(data -> {
            searchPaging(data, form);
        });
    }

    /**

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see