When invoking the link for google maps from seam-comp-showcase and the tree is in Conversation-scope, either Page or Conversation scope should be fine. However, once the link is clicked, the jsf life-cycle is automatically completed and another begun (meaning the start of an entire new conversation so the dataModel for the tree gets re-initialized, etc and the component jspx pages are not shown).

For googlemaps this only happens the first time the application tries to load one of it's jspx pages.

For inputRichText, this happens each time.

Note that these pages are within panelTabSet (as per 1.7.0.Beta1 samples/component-showcase --jspx pages are same).

If the TreeNavigationBean is in Session-scope then the pages load properly, but curiously the backing bean for inputRichText is loaded twice.

Looks like some circumventing of the jsf lifecycle and is very noticeable when using standard request scope.

 I am trying to create seam-comp-showcase with only the style bean as session-scoped, (and to use to test concurrentDomView=true)...this means that each session can have multiple conversations of seam-comp-showcase. For now, with TreeNavigation in session-scope, each window has to view the same state of the tree (no point to use concurrentDomView=true). Nice also to show that all our components can be used outside of Session scope.