[magnolia-dev] [JIRA] (MGNLUI-667) AppController: currentAppInstanceController set too late, causes null pointer
Espen Jervidalo created MGNLUI-667 AppController: currentAppInstanceController set too late, causes null pointer Issue Type: Bug Affects Versions: 5.0 Assignee: Espen Jervidalo Created: 18/Feb/13 10:26 AM Fix Versions: 5.0 Project: Magnolia UI Priority: Neutral Reporter: Espen Jervidalo Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-667) AppController: currentAppInstanceController set too late, causes null pointer
Tobias Mattsson reopened MGNLUI-667 AppController: currentAppInstanceController set too late, causes null pointer I think you're breaking the app history with this change, because now this if statement is always true: if (currentAppInstanceController != nextAppContext) { appHistory.addFirst(nextAppContext); } Also, it might make sense to make doStartIfNotAlreadyRunning() return void instead. Change By: Tobias Mattsson (20/Feb/13 12:07 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: