Details
-
Task
-
Resolution: Fixed
-
Critical
-
5.0
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
Current implementations are not streamlined at all:
- ContentViewBuilderImpl#build should either create all containers or none - currently it's a mix- accessing jcr happens from various places although we could reuse logic: TreeModel, AbstractJcrContainer and LazyThumbnailViewImpl!
- all AbstractJCRContainers require a TreeModel but only HierarchicalContianer should
- TreeModel is a JcrContainerSource? Why not put that logic into HierachicalJcrContainer directly as it's only used there?
Checklists
Acceptance criteria
Attachments
Issue Links
- is causing
-
MGNLDAM-8 Adapt container usage according to refactoring/simplification done in MGNLUI
-
- Closed
-