Skip to content

Jira migration/95 optimize resourse not found exception - #132

Open
PIPetkova19 wants to merge 4 commits into
mainfrom
jira-migration/95-optimize-resourse-not-found-exception
Open

Jira migration/95 optimize resourse not found exception#132
PIPetkova19 wants to merge 4 commits into
mainfrom
jira-migration/95-optimize-resourse-not-found-exception

Conversation

@PIPetkova19

Copy link
Copy Markdown
Contributor

Changes made:

  • Introduced domain-specific NotFoundException classes extending ResourceNotFoundException.
  • Removed ErrorConstants usage and String.valueOf() conversions from services.
  • Updated exception handling to return specific not found messages.

@PIPetkova19 PIPetkova19 self-assigned this Jul 22, 2026
@PIPetkova19
PIPetkova19 requested a review from a team as a code owner July 22, 2026 10:33

@Manastirski Manastirski left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no i18n for the exception messages and they will be shown in English to the clients, consider adding i18n.

@@ -26,13 +26,12 @@ public class GlobalExceptionHandler {
//Handles resource not found exceptions triggered by element not found by search parameters
@ExceptionHandler(ResourceNotFoundException.class)
public ResponseEntity<ErrorResponse> handleValidationException(final ResourceNotFoundException ex,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this method handles resource not found exception, but its called handleValidationException

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants