[MAGNOLIA-1776] Changing template renderers in order to use include instead of forward Created: 11/Oct/07 Updated: 17/Dec/07 Resolved: 11/Oct/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 3.1 M3 |
| Fix Version/s: | 3.5 RC1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| 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 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)
|
||||||||||||||||||||
| Description |
|
The jsp template renderer actually uses a forward in order to render jsps. We will change it in 3.1 in order to include jsps instead of forwaring to them. The simple change is as following: RequestDispatcher rd = request.getRequestDispatcher(requestReceiver);
Note that this could require updating any custom filter mapping (not the magnolia one) you may have mapped to *.jsp only, when upgrading a custom application based on a previous version of magnolia. |
| Comments |
| Comment by Fabrizio Giustina [ 11/Oct/07 ] |
|
fix committed for 3.1 |