[MAGNOLIA-2807] Make ActivationContent clonable Created: 02/Jul/09 Updated: 23/Jan/13 Resolved: 02/Jul/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 4.0.1, 4.1, 3.6.6 |
| Fix Version/s: | 4.0.2, 3.6.7, 3.6.8, 4.1.1 |
| Type: | Improvement | 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)
|
||||||||
| Description |
|
Since ActivationContent can be used from multiple threads simultaneously during activation and it is not inherently thread safe the class should support cloning in order for each activation thread to be able to obtain its own copy. |