[MAGNOLIA-465] Clean up web.xml Created: 20/Jun/05 Updated: 17/Mar/09 Resolved: 10/Aug/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Philipp Bärfuss |
| Resolution: | Duplicate | 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 |
|
web.xml is a mess... we should remove all the dialog servlets and find another way to map them to URIs. |
| Comments |
| Comment by Philipp Bracher [ 21/Jun/05 ] |
|
Dublicates 379. We must do the same for the so called pages as we did for the paragraph & security dialogs:
The classes are in the packages module.adminninterface.pages |
| Comment by Michael Aemisegger [ 21/Jun/05 ] |
|
A nasty comment. What about a proven framework? Sorry, couldn't resist. |
| Comment by Philipp Bracher [ 21/Jun/05 ] |
|
this brings consistency. Would you like to wait for an other half a year until we release 2.1 based on JSF? In later discussions we decided to postpone the introduction of a framework to later versions (we are talking about version 3 something) |
| Comment by Michael Aemisegger [ 21/Jun/05 ] |
|
Sure, I understand. By no means, I wanted to start the discussion again. Just wanted to be annoying and mean. I succeded. Sorry again. |