[MAGNOLIA-1267] commands context is not released if executed via tree actions Created: 12/Dec/06  Updated: 13/Oct/12  Resolved: 13/Oct/12

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sameer Charles Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

according to command API, command can implement release method but its not possible since current commands are inter-dependent.
as a result if you execute a command from gui it sets the context attributes which are not cleaned up on next action.



 Comments   
Comment by Magnolia International [ 10/Jul/08 ]

We should check if this is still the case with 3.6

Comment by Magnolia International [ 20/Jan/09 ]

... and if so, it will have to be postponed until 4.1

Comment by Jan Haderka [ 13/Oct/12 ]

release() method in the command API releases the state of the command, but is not meant to affect the context that was passed to the command. If some command doesn't release it's state properly, open issue against such command directly. Result of executing command, might actually be modification of the context.
If caller means to not have its own context modified by command execution, it should clone the context and pass in the clone.

Generated at Mon Feb 12 03:25:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.