[MAGNOLIA-2893] Review commands to ensure they reset values of their private variables in release() method Created: 13/Oct/09 Updated: 23/Jan/13 Resolved: 13/Oct/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation, admininterface, core, workflow |
| Affects Version/s: | 4.1.1 |
| Fix Version/s: | 4.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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 |
|
Currently most of the commands do not release values of their private variables in the release() method. As the command instances are pooled for later reuse, they might be reused with values of some private variables set incorrectly. This leads to some random, hard to reproduce issues for example in activation. |
| Comments |
| Comment by Jan Haderka [ 13/Oct/09 ] |
|
Done for:
|
| Comment by Philipp Bärfuss [ 13/Oct/09 ] |
|
This is somehow related to |