[MGNLREST-73] When one endpoint definition fails to register, the rest of the to-be-registered endpoint will not get registered. Created: 24/Aug/16  Updated: 08/Mar/17  Resolved: 07/Mar/17

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: 1.2.1

Type: Bug Priority: Blocker
Reporter: Jordie Diepeveen Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Basel 86
Story Points: 3

 Description   

In the RestDispatcherServlet#init (line 112), all currently registered endpoints are being registered to the servlet. During this process, the Endpoint will be initialized. We had a scenario were one of the endpoint could not be initialized properly due to a wrong Generic type. The initialization process did throw a guice error without any real description of the failure, but this was not really the problem.
The servlet threw an exception and did not register the rest of the valid endpoint keeping us in the dark about what in which endpoint did do wrong.

I would like to suggest a try..catch around the line "registerEndpoint(endpointDefinition)" so developers know which Endpoint definition failed to register, and so that the rest of the endpoint are correctly registered (because they are fine).


Generated at Mon Feb 12 06:56:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.