I have tested this in M1 snapshot, 1.0.4 and 1.0.5. It appears that the PageFlowScope is not cleared down when you send clear to the Map. The map looks like it is maintained correctly but old references are still hanging around. I have created a simple tester to illustrate. The tester consists of a page with 3 buttons on it. "Add", "no Add" and "Clear". These buttons are bound to an action on a request scoped bean. The "add" action creates an instance of a class and puts it in pageflowscope under the name "flowScopeObject". This mean that each time the button is clicked, the object gets replaced in the map. The page also shows how many of these objects are in the map as given to it from the pageFlowScope. "no Add" simply runs an action navigating back to the same page and "clear" runs an action that clears the map.
>From a client perspective all works fine. The list of items in the map appears to be correct. When you click "add" the item is replaced but there is still only one item. When you click "clear" no items exist and when you then click "no Add" there are still no items. JProfiler has found however that the added objects are accumulating. I can use this application to find paths back to the GC and they are all linked back to PageFlowScopeMap and ultimately http session. Also of note is that the Map itself is a different instance everytime and the clear implementation does not appear to do anything special and so clearing the current Map wouldn't clear other Maps that are related. -- View this message in context: http://www.nabble.com/-Trinidad--PageFlowScope-not-clearing-down-tp15040029p15040029.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
