Seam-Wicket integration and conversation scope

[paolodt]

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

[pmuir]

paolo di tommaso wrote on Mar 23, 2008 08:15 PM:


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.

Yup. I need to find time to work on it again.

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.

Try using SeamLink for now (you would need to implement a similar component for the Ajax version). Yes, propagating the conversation needs to be available for all the built in Wicket components. File a feature request in JIRA - even better, if you find a way to do it, attach a patch!

[paolodt]

Pete,
thank you for replying.

I've opened a Jira request for this:

http://jira.jboss.org/jira/browse/JBSEAM-2782

I've tried to find a patch to this issue but it requires a  guru knowledge on both Seam and Wicket .. ;)

Have you tried to involve someone from core wicket developers? They should be really interested about that.

Thank you.

// Paolo