Mike Kienenberger wrote: > You'd need to address backtracking and page refreshing issues as well. > Well there is also the problem of having to deal with double opened windows... Which means you run the system into a state where the object has to be garbage collected while the other window still is within the scope, thus you force a garbage collection of the object way to early. (Btw. a problem which also should exist in x:saveState)
I had a very similar mechanism in my last Struts based project, because Struts dialogs did not do it for me (I found out it did not garbage collect the scoped objects until the session ran out), using a servlet filter. I gracefully omitted the problem yet, because I could not entirely figure out how to deal with it. What is the general consensous on solving this issue. I really have to look into spring dialog, and seam sources they probably have had solved this issue.
