[MAGNOLIA-385] saving dialogs leads to nullpointer exception Created: 09/May/05 Updated: 17/Mar/09 Resolved: 09/May/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.1 Final |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| 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 |
|
java.lang.NullPointerException Seams to belong to the same problem: When I try to edit a page in the sample website I get the following errors: ERROR info.magnolia.module.admininterface.DialogMVCServlet 07.05.2005 17:37:05 – no config node found for dialog : samplesPageFooter |
| Comments |
| Comment by Fabrizio Giustina [ 09/May/05 ] |
|
Hi Philipp I added a better error handling in the code so that at least a specific exception is thrown (instead of NPEs in the log), but I don't know exactly how it is supposed to work (why isn't dialog handler optional?), can you give it a look? |
| Comment by Philipp Bracher [ 09/May/05 ] |
|
fixed with a ugly workaround in DialogMVCServlet. I will register a new task to remove this: //TODO remove this code!!! we should register the dialgos during startup // END of the workaround |