Uses of Class
ca.uhn.fhir.rest.server.exceptions.BaseServerResponseException

Packages that use BaseServerResponseException

Package	Description
ca.uhn.fhir.fluentpath
ca.uhn.fhir.rest.client.exceptions
ca.uhn.fhir.rest.server.exceptions

Uses of BaseServerResponseException in ca.uhn.fhir.fluentpath

Subclasses of BaseServerResponseException in ca.uhn.fhir.fluentpath

Modifier and Type	Class	Description
class	FluentPathExecutionException	This exception is thrown if a FluentPath expression can not be executed successfully for any reason

Uses of BaseServerResponseException in ca.uhn.fhir.rest.client.exceptions

Subclasses of BaseServerResponseException in ca.uhn.fhir.rest.client.exceptions

Modifier and Type	Class	Description
class	FhirClientConnectionException	Represents a failure by the HAPI FHIR Client to successfully communicate with a FHIR server, because of IO failures, incomprehensible response, etc.
class	FhirClientInappropriateForServerException	This exception will be thrown by FHIR clients if the client attempts to communicate with a server which is a valid FHIR server but is incompatible with this client for some reason.
class	InvalidResponseException
class	NonFhirResponseException

Uses of BaseServerResponseException in ca.uhn.fhir.rest.server.exceptions

Subclasses of BaseServerResponseException in ca.uhn.fhir.rest.server.exceptions

Modifier and Type	Class	Description
class	AuthenticationException	Represents an HTTP 401 Client Unauthorized response, which means that the client needs to provide credentials, or has provided invalid credentials.
class	ForbiddenOperationException	This Represents an HTTP 403 Forbidden response, which generally indicates one of two conditions: Authentication was provided, but the authenticated user is not permitted to perform the requested operation. The operation is forbidden to all users.
class	InternalErrorException	Represents an HTTP 500 Internal Error response.
class	InvalidRequestException	Represents an HTTP 400 Bad Request response.
class	MethodNotAllowedException	Represents an HTTP 405 Method Not Allowed response.
class	NotImplementedOperationException	This Represents an HTTP 501 Not Implemented response, which means the resource provider currently lacks the ability to fullfill the request.
class	NotModifiedException	This Represents an HTTP 301 Not Modified response, which means the resource has not changed since the last version the client retrieved.
class	PayloadTooLargeException	This Represents an HTTP 413 Payload Too Large response, which means the request body was too big for the server to accept
class	PreconditionFailedException	Represents an HTTP 412 Precondition Failed response.
class	ResourceGoneException	Represents an HTTP 410 Resource Gone response, which geenerally indicates that the resource has been deleted
class	ResourceNotFoundException	Represents an HTTP 404 Resource Not Found response, which means that the request is pointing to a resource that does not exist.
class	ResourceVersionConflictException	Represents an HTTP 409 Conflict response.
class	ResourceVersionNotSpecifiedException	Deprecated. Use PreconditionFailedException instead - This exception is strangely named and will be removed at some point.
class	UnclassifiedServerFailureException	Exception for use when a response is received or being sent that does not correspond to any other exception type.
class	UnprocessableEntityException	Represents an HTTP 422 Unprocessable Entity response, which means that a resource was rejected by the server because it "violated applicable FHIR profiles or server business rules".

Methods in ca.uhn.fhir.rest.server.exceptions that return BaseServerResponseException

Modifier and Type	Method	Description
BaseServerResponseException	BaseServerResponseException.addResponseHeader(String theName, String theValue)	Add a header which will be added to any responses
static BaseServerResponseException	BaseServerResponseException.newInstance(int theStatusCode, String theMessage)
BaseServerResponseException	BaseServerResponseException.setErrorMessageTrusted(boolean theErrorMessageTrusted)	This flag can be used to signal to server infrastructure that the message supplied to this exception (ie to the constructor) is considered trusted and is safe to return to the calling client.