[BLOSSOM-159] NPE when opening a new dialog Created: 28/Jan/14 Updated: 06/Dec/14 Resolved: 29/Jan/14 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.0.3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Jean-Charles Robert | Assignee: | Tobias Mattsson |
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
It's impossible with version 2.0.2 to add a new component (in author mode) bescause the dialog is failing. I patched the class by replacing this line that simply tests if the node is null, and it solved the problem. BlossomConfiguredDialog#createDialog //context.setContentNode(storageNode.getJCRNode()); context.setContentNode(storageNode != null ? storageNode.getJCRNode() : null);
|
| Comments |
| Comment by Tobias Mattsson [ 29/Jan/14 ] |
|
Thanks for reporting this Jean-Charles. Version 2.0.3 has just been released to address this issue. |
| Comment by Jan Haderka [ 06/Dec/14 ] |
|
Bulk close of old resolved tickets. |