* @return {@link ArtifactResolverResult}
     * @throws ArtifactResolverException in case of an error
     * @throws IllegalArgumentException in case of parameter {@code buildingRequest} is {@code null} or
     *             parameter {@code mavenArtifact} is {@code null} or invalid
     */
    ArtifactResolverResult resolve(ArtifactResolverRequest request);

    /**

Als Teil der Erstellung des Anwendungsobjekts wird eine *Pfadoperation* für `/openapi.json` (oder welcher Wert für den Parameter `openapi_url` gesetzt wurde) registriert.

But you still want to be able to filter and convert the data you return with a `response_model`.

For those cases, you can use a `Response` parameter.

## Use a `Response` parameter { #use-a-response-parameter }

You can declare a parameter of type `Response` in your *path operation function* (as you can do for cookies and headers).

And then you can set the `status_code` in that *temporal* response object.

     * Even if empty string, treated as empty plainly. So "IF pmb != null" is false if empty.
     * @param clustername The parameter value of clustername. (NotNull)
     */
    public void setClustername(String clustername) {
        registerVariable("clustername", clustername);
    }

    /**
     * Set the value of clusterstatus, used in parameter comment. <br>

                if (oldNullability && !newNullability) {
                    errors << "Parameter $idx from null accepting to non-null accepting breaking change".toString()
                } else if (!oldNullability && newNullability) {
                    warnings << "Parameter $idx nullability changed from non-nullable to nullable".toString()
                }
            }
        }

You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.

It takes a list containing one dictionary for each tag.

Each dictionary can contain:

* `name` (**required**): a `str` with the same tag name you use in the `tags` parameter in your *path operations* and `APIRouter`s.

                "Method com.example.Source.foo(java.lang.String): Parameter 0 from null accepting to non-null accepting breaking change.",
                "Method com.example.Source.setSomeVar(java.lang.String): Parameter 0 from null accepting to non-null accepting breaking change.",
                "Constructor com.example.Source(java.lang.String): Parameter 0 from null accepting to non-null accepting breaking change."
            )

# Response-Cookies { #response-cookies }

## Einen `Response`-Parameter verwenden { #use-a-response-parameter }

Sie können einen Parameter vom Typ `Response` in Ihrer *Pfadoperation-Funktion* deklarieren.

Und dann können Sie Cookies in diesem *vorübergehenden* <abbr title="Response – Antwort: Daten, die der Server zum anfragenden Client zurücksendet">Response</abbr>-Objekt setzen.

{* ../../docs_src/response_cookies/tutorial002_py39.py hl[1, 8:9] *}

labels.crawlingConfigName=Nama
labels.crawlingConfigPath=Jalur untuk Dirayapi
labels.processType=Jenis Proses
labels.parameters=Parameter
labels.designFile=Berkas untuk Diunggah
labels.bulkFile=Berkas Bulk
labels.appendQueryParameter=Tambahkan Parameter Pencarian
labels.configId=ID Konfigurasi
labels.configParameter=Parameter Konfigurasi
labels.content=Konten
labels.csvFileEncoding=Encoding CSV
labels.defaultLabelValue=Label Default

    * The router dependencies are executed first, then the [`dependencies` in the decorator](dependencies/dependencies-in-path-operation-decorators.md){.internal-link target=_blank}, and then the normal parameter dependencies.
    * You can also add [`Security` dependencies with `scopes`](../advanced/security/oauth2-scopes.md){.internal-link target=_blank}.

/// tip