When closing the new impl of detail sub-app, the whole admincentral is prone to get corrupted since IoC context of the root sub-apps view isn't set up properly: the view is not created via framework utility (unlike browser sub-app case) and framework fails to determine the context reference of it, ending up falling back to the default (which is the whole admincentral scope) and possibly cleaning up the whole bean store, blowing up admincentral session.

Solution suggestion:

• make sure that the root view of details sub-app is created with framework tools (e.g. view provider) and its context reference is allocated.
• do a post-mortem, see how the situation could be mitigated (e.g. choose better defaults for the fallback IoC context)
• consider providing base implementations of the sub-app that come with pre-set root views, configured properly IoC-wise. This is a good to do step, since framework users shouldn't care about things that the framework is able to provide out of the box.