</table>
                                    </div>
                                </div>
                                <div class="row">
                                        <%-- Paging Info --%>
                                    <div class="col-sm-2">
                                        <la:message key="labels.pagination_page_guide_msg"

        dataConfigPager.clear();
        return asHtml(path_AdminDataconfig_AdminDataconfigJsp).renderWith(data -> {
            searchPaging(data, form);
        });
    }

    /**
     * Search with paging.
     * @param data The render data.
     * @param form The search form.
     */
    protected void searchPaging(final RenderData data, final SearchForm form) {

#                                                     Paging
#                                                     ------

# The size of one page for paging
paging.page.size = 25

# The size of page range for paging
paging.page.range.size = 5

# The option 'fillLimit' of page range for paging
paging.page.range.fill.limit = true

# fetch page size

   *       and virtual memory, this is not a problem - because it is mapped read-only, the kernel
   *       can always page it to disk "for free". However, on systems where killing processes
   *       happens all the time in normal conditions (i.e., android) the OS must make a tradeoff
   *       between paging memory and killing other processes - so allocating a gigantic buffer and

    /** The key of the configuration. e.g. 25 */
    String PAGING_PAGE_SIZE = "paging.page.size";

    /** The key of the configuration. e.g. 5 */
    String PAGING_PAGE_RANGE_SIZE = "paging.page.range.size";

    /** The key of the configuration. e.g. true */
    String PAGING_PAGE_RANGE_FILL_LIMIT = "paging.page.range.fill.limit";

    /** The key of the configuration. e.g. 1000 */

    // ============================================================
    // Request and Search Constants
    // ============================================================

    /** Paging query list parameter name. */
    public static final String PAGING_QUERY_LIST = "pagingQueryList";

    /** Request languages parameter name. */
    public static final String REQUEST_LANGUAGES = "requestLanguages";

Since the naming of the properties no longer suggests they are experimental, we want to ensure users are aware if the current property stops having an effect.
Since the underlying feature is incubating, its actual behavior can still change or be removed in the minor releases.

These properties CAN be supplemented with command-line options and they SHOULD follow the shared naming scheme described above.

* `swagger_js_url`: a URL onde a página HTML para a sua documentação do Swagger UI pode obter o arquivo **JavaScript**. Este é o URL do CDN personalizado.
* `swagger_css_url`: a URL onde a página HTML para a sua documentação do Swagger UI pode obter o arquivo **CSS**. Este é o URL do CDN personalizado.

E de forma semelhante para o ReDoc...

Ahora puedes crear las *path operations* para la documentación personalizada.

Puedes reutilizar las funciones internas de FastAPI para crear las páginas HTML para la documentación, y pasarles los argumentos necesarios:

* `openapi_url`: la URL donde la página HTML para la documentación puede obtener el OpenAPI esquema de tu API. Puedes usar aquí el atributo `app.openapi_url`.
* `title`: el título de tu API.

labels.advance_search_filetype_excel=MS Excel
labels.advance_search_filetype_powerpoint=MS PowerPoint
labels.advance_search_occt=Buscar en
labels.advance_search_occt_default=Página completa
labels.advance_search_occt_allintitle=Título de la página
labels.advance_search_occt_allinurl=URL de la página
labels.advance_search_sitesearch=Sitio o dominio
labels.advance_search_timestamp=Fecha de actualización
labels.advance_search_timestamp_default=Cualquier fecha