...but continue reading below to see how to overcome that.

## Return Type and Data Filtering { #return-type-and-data-filtering }

Let's continue from the previous example. We wanted to **annotate the function with one type**, but we wanted to be able to return from the function something that actually includes **more data**.

    /**
     * Default constructor.
     */
    public FessSearchAction() {
        super();
    }

    /** The field name used for label-based search filtering. */
    protected static final String LABEL_FIELD = "label";

    /** Helper for performing search operations and managing search requests. */
    @Resource
    protected SearchHelper searchHelper;

            return getAllWebConfigList();
        }
        return getAllWebConfigList(true, true, false, idList);
    }

    /**
     * Retrieves web crawling configurations with various filtering options.
     *
     * @param withLabelType whether to include label type information (currently not used in implementation)

    }

    /**
     * Generates URL query parameters for facet filtering.
     *
     * @return URL-encoded query string containing facet parameters
     */
    public static String facetQuery() {
        return createQuery(Constants.FACET_QUERY, FACET_PREFIX);
    }

    /**
     * Generates URL query parameters for geographic filtering.
     *

- **Extensible Architecture**: Plugin system for custom extractors, transformers, and clients
- **Rate Limiting**: Politeness policies and interval controllers
- **URL Filtering**: Regex-based inclusion/exclusion patterns
- **Data Persistence**: Multiple backend options including OpenSearch integration

## Technology Stack

- **Java**: 21+ (requires Java 21 or higher)

     * This method applies role-based filtering to ensure users only see documents they have access to.
     *
     * @param queryContext the query context to modify
     * @param searchRequestType the type of search request to determine role filtering requirements
     */

                <resource>
                  <directory>../../guava</directory>
                  <includes>
                    <include>module.json</include>
                  </includes>
                  <filtering>true</filtering>
                </resource>
              </resources>
            </configuration>
          </execution>
        </executions>
      </plugin>
      <plugin>

      if (to != Bound.NO_BOUND) {
        extremeValues.add(delegate.aboveSamplesLesser());
        extremeValues.add(delegate.aboveSamplesGreater());
      }

      // the regular values should be visible after filtering
      List<@Nullable Object> allEntries = new ArrayList<>();
      allEntries.addAll(extremeValues);
      allEntries.addAll(normalValues);
      SortedSet<E> set = delegate.create(allEntries.toArray());

 *
 * <p>The parser handles the following GSA configuration elements:
 * <ul>
 * <li>Collections with good/bad URL patterns</li>
 * <li>Global parameters including start URLs and filtering rules</li>
 * <li>User agent settings</li>
 * <li>URL pattern matching with regular expressions and contains filters</li>
 * </ul>
 *
 */
public class GsaConfigParser extends DefaultHandler {

É por isso que neste exemplo temos que declará-lo no parâmetro `response_model`.

...mas continue lendo abaixo para ver como superar isso.

## Tipo de Retorno e Filtragem de Dados { #return-type-and-data-filtering }

Vamos continuar do exemplo anterior. Queríamos **anotar a função com um tipo**, mas queríamos poder retornar da função algo que realmente incluísse **mais dados**.