[MAGNOLIA-34] Refactor control objects (Gui-Classes) Created: 11/Aug/04 Updated: 23/Jan/13 Resolved: 21/Oct/04 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.0 Final |
| Type: | Improvement | Priority: | Major |
| Reporter: | Pascal Mangold | Assignee: | Fabrizio Giustina |
| 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: |
| Comments |
| Comment by Philipp Bracher [ 14/Mar/05 ] |
|
As I have seen so far, there is a lot of html-code inside the java-classes. I like the ascpect, that we have control-classes, but i would like it much more if they would render using some template mechanisms. Since JSP's can't be called without passing a request-object, we can not call them inside the getHtml() methods. Or does somebody knows such a solution. Here are some ideas: a) passing the request to the getHTML() method (they are recursive) b) using an other mechanism c) The control defines a JSP file witch is called and the control-object is passed to this page d) ... |