spring webflow's approach really seems interesting, i wonder if that could become a seam feature one day?
we had also a hard time to implement a wizard in a popup div with conversation scoped components; we then switched from using a nested conversation to the use of
<a4j:keepAlive beanName="aBean" />
this tag extends the event scope for aBean over all following ajax-requests.
we would have preferred using a nested conversation as this is the native seam scope, and this extended event scope feels like an additional scopetype. but it solved our problems.
how do other seam users scope components/backing beans, that are only needed within a popup wizard?