[MAGNOLIA-839] Exceptions caught by Dispatcher.dispatch() in EntryServlet fail to result in an error page Created: 07/May/06 Updated: 23/Jan/13 Resolved: 29/May/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1.5 |
| Fix Version/s: | 3.0 RC1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Sterling Hanenkamp | Assignee: | Sameer Charles |
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
If a page called by the dispatcher throws an exception that results in either ServletException or IOException or any RuntimeException to be thrown back up into EntryServlet, they are all caught as Exception and logged and ignored. As such, these result in a blank page. I would suggest that the correct behavior is to log the error and then rethrow these exceptions or send an error response. |
| Comments |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
This is anyoing |
| Comment by Sameer Charles [ 29/May/06 ] |
|
there is no separate Dispatcher for 3.0, adopted EntryServet to log and throw repository exception as ServletException |