You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Enhancement] [ANCHOR: BE JAVA] Move Resources Exception Handling to Global Exception Handler and Standardize Exception Thrown in the Resources Feature
#1194
Description
Move the exception handling logic for the Resources feature to the global exception handler. Standardize the exceptions thrown within the Resources feature to ensure consistent error handling across the platform. Acceptance Criteria
The Resources feature should no longer contain specific exception handling logic within its classes.
All exceptions in the Resources feature are routed through the global exception handler.
Standardized exception messages and statuses are used for all Resources-related errors. Purpose
To centralize exception handling, making it easier to maintain and ensure consistent error responses across the platform. Requirements
Refactor the Resources feature to remove specific exception handling logic.
Implement standardized exceptions for all error cases within the Resources feature.
Ensure all exceptions are correctly handled by the global exception handler. Expected Outcome
Exception handling in the Resources feature is centralized and standardized, leading to more consistent error management across the platform.
The text was updated successfully, but these errors were encountered:
Description
Move the exception handling logic for the Resources feature to the global exception handler. Standardize the exceptions thrown within the Resources feature to ensure consistent error handling across the platform.
Acceptance Criteria
Purpose
To centralize exception handling, making it easier to maintain and ensure consistent error responses across the platform.
Requirements
Expected Outcome
Exception handling in the Resources feature is centralized and standardized, leading to more consistent error management across the platform.
The text was updated successfully, but these errors were encountered: