Loading...

XML

Word

Printable

Type: Story
Resolution: Fixed
Priority: Major
Fix Version/s: 5.3
Affects Version/s: 5.2
Component/s: content app, framework
Labels:
- next

Template:
Acceptance criteria:

Empty

show more show less
Task DoD:

show more show less
Epic Link:
JCR-agnostic content apps
Sprint:
5.3 Preparation 2, 5.3 Sprint 3, 5.3 Sprint 4

Item selection and other item operations including action availability checking should not depend on JCR API and JcrItemAdapters so that the developers of custom non-JCR related apps could use BrowserSubApp and BrowserPresenter out of the box.

Acceptance criteria

is related to

MGNLUI-2680 Make ImageProvider interface JCR-agnostic

Closed

MGNLUI-2699 Implement Voter-based availability checking system.

Closed

MGNLUI-2724 Make Jcr implementation of content apps use more descriptive item ids.

Closed

is superseded by

MGNLUI-2569 As a developer, I can configure and/or extend content app components to work with non-JCR data sources, so that I can integrate other services into apps easily.

Closed

relates to

MGNLUI-2662 Get rid of javax.jcr.Item dependency in ActionExecutor interface, its abstract implementation and AvailabilityRules.

Closed

MGNLUI-2664 Extract JCR-specific implementation details of Workbench into a child class still exposing the public functionality

Closed

mentioned in: Wiki Page Loading...

(1 relates to, 1 mentioned in)

Assignee:: Aleksandr Pchelintcev

Reporter:: Aleksandr Pchelintcev

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 07/Feb/14 3:19 PM

Updated:: 20/Mar/14 3:18 PM

Resolved:: 13/Mar/14 3:47 PM

Task DoD

Details

Description

Checklists

Attachments

Issue Links

Activity

People

Dates

Checklists