Built-in exception classes¶
NOTE: do not raise framework exceptions yourself - otherwise the components might misbehave.
Framework itself raises a bunch of errors that give a descriptive information regarding the status of triggered operations.
NOTE: the framework does not wrap any internal errors within implementations - they are raised without any changes.
Copyright (c) 2014-2015 F-Secure See LICENSE for details
- exception resource_api.errors.AuthorizationError¶
Raised when user is not allowed to perform a specific operation with resource instance or resource collection
- exception resource_api.errors.DataConflictError¶
Raised when user tries to perform something that conflicts with a current state of data - create Resource or Link that was already create before
- exception resource_api.errors.DeclarationError¶
Raised by the framework during initialization phase if there are some issues with declarations
- exception resource_api.errors.DoesNotExist¶
Raised when trying to fetch a non-existent Resource or Link instance
- exception resource_api.errors.Forbidden¶
Raised whenever user tries to perform something that is prohibited due to the structure of data - remove required LinkToOne - create one to many link
- exception resource_api.errors.FrameworkError¶
Base class for all the errors that are raised by the framework
- exception resource_api.errors.MultipleFound¶
Raised when user tries to fetch link to one instance and the framework manages to find multiple entries
- exception resource_api.errors.ResourceDeclarationError(resource, message)¶
Raised by the framework when there are issues with resource declarations
- exception resource_api.errors.ValidationError¶
Raised for any issue related to data sent by user including linking errors