-
Bug
-
Resolution: Fixed
-
Neutral
-
2.0.7
-
None
MGNLDAM-523 introduced this new interface, but it's flawed. It was added without the understanding that something was missing before:
- JcrAssetProvider should be implementing getRendererFor()
RenditionAwareAssetProvider adds a method that looks like a shortcut for the above, except that it also prevents using the whole system correctly
:
AssetProviderRegistry.getRendererFor(myAsset, MediaType.JPEG).render(myAsset, MediaType.JPEG, "myRenditionName")
(i see the verbosity/redundancy, for which we could add a shortcut in APR)
I'd like to deprecate this interface ASAP, and remove it in 2.1, since it just creates noise and confusion.
STK has an implementation of this, which should also go.
In addition, we'll need:
- a default renderer that knows about our imaging module
- a noop renderer so there is always at minimum one renderer which does nothing.
- relates to
-
MGNLDAM-555 Add asset renderer that does nothing but render a rendition of the original asset (no-op)
- Closed
-
MGNLDAM-554 Add asset renderer that knows about imaging module
- Closed
-
MGNLDAM-556 RenditionWrapper should extend new interface AssetRendition in order to be usable by new DAM API
- Closed
-
MGNLSTK-1469 Use asset renderers from DAM
- Closed
-
MGNLSTK-1471 Adjust STK to work with new renderers from DAM
- Closed
- supersedes
-
MGNLDAM-523 Add new asset provider capability - rendition awareness
- Closed
- mentioned in
-
Page Loading...