[MGNLIMG-150] Extract Imaging entry point from ImagingServlet Created: 10/Mar/15  Updated: 25/Jul/17  Resolved: 16/May/16

Status: Closed
Project: Imaging
Component/s: None
Affects Version/s: None
Fix Version/s: 3.3

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLIMG-199 Cache can not be disabled anymore Open
dependency
is depended upon by MGNLIMG-81 Provide link generator Closed
is depended upon by MGNLIMG-155 Expose available ImageIO plugins via ... Closed
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)
Date of First Response:
Sprint: Kromeriz 43
Story Points: 2

 Description   

There are use cases where we want to generate images without going through a new request and the ImagingServlet (e.g tests, Vaadin components, ability to pre-generate images, ...). A lot of the logic currently baked in the servlet could be extracted in a simple component.

This should also facilitate link generation



 Comments   
Comment by Magnolia International [ 08/Oct/15 ]

Done on branch feature/MGNLIMG-150_ExtractEntryPoint.

Further improvements:

  • ImageResponse vs ImageGenerationJob and a refactoring of the "caching" mechanism (decouple the locking/threading code from the code that loads and saves from/to JCR)
  • Rework how parameters are bound to generation chains - they should be decoupled
Comment by Philip Mundt [ 19/Jul/17 ]

cmeier would it be possible to amend information about this change to the release notes?

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