[MGNLREST-76] Swagger 1.5.10 Created: 26/Sep/16  Updated: 29/Sep/16  Resolved: 27/Sep/16

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

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Cedric Reichenbach
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Swagger API Update
Sprint: Basel 63
Story Points: 1

 Description   

tbd.



 Comments   
Comment by Cedric Reichenbach [ 26/Sep/16 ]

Updating from 1.5.4 to 1.5.10 is problematic, since caching of the Swagger instance has been refactored, and it's unclear how exactly it works now, thus hard to flush.

  • If SwaggerConfigLocator is used (which was the case in a quick debugging session), resetting the Swagger instance will not be possible without reflection hacks.
  • Even though servlet context is still checked for a Swagger object, it's never put there anymore. However, this behavior is most probably unintended and might change again soon (see my question).

A large portion of profound changes (affecting us) were introduced as of 1.5.7, so an update with reasonable effort could only be done up to 1.5.6.

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