CDIUI Re-entry problem

The problem

A demo is attached. To re-produce the problem:

(1) go to start page, and be forwarded to #!login view

(2) click "Sign in", meet breakpoint at MainView.initialize(), thisMainView(id 459); continue to show the page, so far so good

(3) Re-enter UI, change browser URL to http://localhost:8080/EdisonSys/ again

• debug output

10:23:48,887 INFO [stdout] (default task-26) initializing UI

10:23:48,888 INFO [stdout] (default task-26) Navigating to MAIN

10:23:48,915 INFO [stdout] (default task-26) WorkSpace, constructor

10:23:48,915 INFO [stdout] (default task-26) Navigating to start, INPUT

10:23:48,918 INFO [stdout] (default task-26) Refreshing NewOrLoad View

10:23:48,921 INFO [stdout] (default task-26) Entering NewOrLoad View

10:23:48,923 INFO [stdout] (default task-26) WorkSpace, constructor done

• break at MainView.initialize(), this = MainView(id=505), it's invoked by MainUi.updateContent() line 56 "navigator.navigateTo(ViewCat.MAIN);"
• continue
• breakpoint again at MainView.initialize(), this = MainView(id=603), cannot find any MY code causing it, but what's MainUi(UI).doInit() line 692??? ok it's actually inherited from class UI line 692, so let me check...
• ok, this is the logic:
  • doInit first calls init(request) which is implemented by my MainUI.
  • in my MainUI, I called updateContent(), which according to state, called navigator.navigateTo(ViewCat.MAIN)
  • after that, doInit() continues and finds an attached navigator. It then called "navigator.navigateTo(navigator.getState())" to go to its kickstart state
  • the chain of command seems to be: that UI super class calls vavigator, which calls CDIViewProvider to obtain a view, and since this MainView is not annotated of any scope, it's dependent scope... and a new instance is created and initialized...
  • continue
  • Exception

Caused by: java.lang.IllegalArgumentException: Component cannot be added inside it's own content

at com.vaadin.ui.AbstractSingleComponentContainer.setContent(AbstractSingleComponentContainer.java:133)

at com.vaadin.navigator.Navigator$SingleComponentContainerViewDisplay.showView(Navigator.java:229)

at com.vaadin.navigator.Navigator.navigateTo(Navigator.java:616)

at com.vaadin.navigator.Navigator.navigateTo(Navigator.java:580)

at com.vaadin.ui.UI.doInit(UI.java:692)

at com.vaadin.server.communication.UIInitHandler.getBrowserDetailsUI(UIInitHandler.java:214)

at com.vaadin.server.communication.UIInitHandler.synchronizedHandleRequest(UIInitHandler.java:74)

at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)

at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1414)

• ok, the cause is WorkSpace (extends AbstractSingleComponentContainer).setContent() line 113, the content being set is an instance (second initialised instance) MainView, and line 113 is after checked isOrHasAncestor(content). How can WorkSpace has ancestor MainView?
• checking variables, YES!!!! Navigator has a parent MainView, exactly that MainView instance.... since when???!!!
• Ok, little bit studying the Navigator code, I am abusing the Navigator class. There should be just one navigator per UI. In addition, I should not override the navigator property of the super UI class.