[MAGNOLIA-1039] commands: use properties to facilitate commands coding Created: 11/Sep/06 Updated: 23/Jan/13 Resolved: 13/Sep/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 RC3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | 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)
|
| Date of First Response: |
| Description |
|
| Comments |
| Comment by Philipp Bracher [ 11/Sep/06 ] |
|
done. to avoid instantiating or synchronization I use an object pool. The original command is used as a prototype. commands can now get coded by using properties which makes them more transparent. |
| Comment by Philipp Bracher [ 13/Sep/06 ] |
|
The pooling fails if the command is not instantiable (for cloning). This is the case if you create anonymous classes for example. In that case we need to synchronize:
|
| Comment by Philipp Bracher [ 13/Sep/06 ] |
|
change commited |