I'm playing with the latest Seam release (2.1.0.A1) containing a really interesting integration of Apache Wicket.
The current implementation appear to be really promising and I hope it will improved in next release. One of the most interesting feature already implemented is the conversation scope that enables conversation-scoped persistent context. I've noticed that the conversation between different wicket pages is maintained only navigating by a form submit action BUT it doesn't when moving between pages using other components i.e. Link, AjaxLink, Button, AjaxBehavior .. and so on. This makes it useless, in particular with Ajax interactions where it is expected to have the maximum benefits (no more LazyInitializationException .. ). Is this a know issue? It is planned in next release to maintained the conversation between Wicket pages navigating by Link and AjaxBehavior also? Thank you, // Paolo
