[MAGNOLIA-3080] Cleanup conundrum between FreemarkerHelper and FreemarkerConfig Created: 15/Feb/10 Updated: 23/Jan/13 Resolved: 12/Mar/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, freemarker |
| Affects Version/s: | None |
| Fix Version/s: | 4.3 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| 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 DoR: |
Empty
|
||||||||||||||||||||||||||||
| Description |
|
Now that Components returns proxies for observed objects, and that ObservedComponentFactory is able to return a default implementation for non-existing nodes (at least for concrete classes), we can finally cleanup the mess between those 2 components. |
| Comments |
| Comment by Magnolia International [ 15/Feb/10 ] |
|
next step: fix dependency between MagnoliaObjectWrapper and FreemarkerConfig |
| Comment by Magnolia International [ 16/Feb/10 ] |
|
If anything, we could now merge these two classes (thus FreemarkerHelper would become observed)
|
| Comment by Magnolia International [ 12/Mar/10 ] |
|
Fine for now - much better than it was. We still need a slightly awkward set of wrappers for freemarker.Configuration but it's now documented and seems cleaner. |