[JCRTOOLS-43] Subapps could use action executor Created: 12/May/17  Updated: 29/Mar/22  Resolved: 22/May/17

Status: Closed
Project: JCR Tools
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1.1

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-4208 Deny or warn when exporting binaries 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)
Epic Link: YAML bootstrap & binaries
Sprint: Kromeriz 97
Story Points: 3
Team: Nucleus

 Description   

Jcr Tools subapps use commands directly.
This involves injecting bunch of components (CommandManager, uiContext, SimpleTranslator) and setting the params manually.
Most of the code is a duplicate of similar actions (ExportAction).
This means that every change in a command has to be reflected in the corresponding action and in this module.
We already have a mechanism to run actions/commands (ActionExecutor) which we should use.
The above applies for import and export sub app, the other two inject the command manager without actually using it.


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