[MGNLUI-1029] Refactor Action classes so that all of them require Vaadin Item instead of javax.jcr.Item or Node. Created: 04/Apr/13  Updated: 25/Jun/13  Resolved: 05/Apr/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: actions, beta1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLUI-1057 Actions in configuration app are broken Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

While most of the Actions require Vaadin Item, some Actions (e.g CreateItemAction) still requires JCR Node as a constructor parameter. In order to avoid problems with ActionExecutor and for consistency reasons we should make all the actions to require Vaadin Item, and access the JCR Node by means of it.


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