concept for future magnolia (possibly 3.5)
(MAGNOLIA-587)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
In the concept draft a lot of details are missed where the commands are described. Here I propose based on a mail from Andreas to use Apache Commons Chain. At the first glimpse this looks realy nice and we would use a well known solution for this kind of problems. |
| Comments |
| Comment by Philipp Bracher [ 09/Dec/05 ] |
|
After some reflections I think this brings more problems than it solves. There are a few places where we still could use this approach. Since we are introducing some neutral model classes like TreeModel, it is easy to make a subclass and configure magnolia without adding this additional concept. Some guys already started to integrate the OpenWFE engine and this brings much more flexibility than this approach does. Still this approach is not dead but has in my opinion no priority |