Uses of Package
io.camunda.zeebe.client.impl.http
Packages that use io.camunda.zeebe.client.impl.http
Package
Description
-
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.implClassDescriptionThin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are always
ProblemDetail, content type is always JSON, etc. -
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.impl.commandClassDescriptionThin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are always
ProblemDetail, content type is always JSON, etc. -
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.impl.fetchClassDescriptionThin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are always
ProblemDetail, content type is always JSON, etc. -
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.impl.httpClassDescriptionRepresents a possible response entity from the Zeebe REST API, either a successful response of type
ApiEntity, or aProblemDetailreturned by the server.Thin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are alwaysProblemDetail, content type is always JSON, etc.Implements aZeebeFuturerepresenting a HTTP call.A generic interface for consuming API entities from an asynchronous data stream. -
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.impl.search.queryClassDescriptionThin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are always
ProblemDetail, content type is always JSON, etc.Implements aZeebeFuturerepresenting a HTTP call. -
Classes in io.camunda.zeebe.client.impl.http used by io.camunda.zeebe.client.impl.workerClassDescriptionThin abstraction layer on top of Apache's HTTP client to wire up the expected Zeebe API conventions, e.g. errors are always
ProblemDetail, content type is always JSON, etc.