[
http://jira.jboss.com/jira/browse/JBSEAM-2782?page=comments#action_12412716 ]
paolo di tommaso commented on JBSEAM-2782:
------------------------------------------
Pete. I cannot manage the diff as you are requiring. I've attached the modified
source.
Anyway my patch is really simple. I've just added all the ListenerInterface that
should propagate the conversionId
:
if ( name.equals(IFormSubmitListener.INTERFACE.getName()) ||
name.equals(ILinkListener.INTERFACE.getName()) ||
name.equals(IBehaviorListener.INTERFACE.getName()) ||
name.equals(IOnChangeListener.INTERFACE.getName()) )
{
:
}
Wicket application should support conversation propagation for all
built components
-----------------------------------------------------------------------------------
Key: JBSEAM-2782
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2782
Project: Seam
Issue Type: Feature Request
Components: Wicket
Affects Versions: 2.1.0.A1
Reporter: paolo di tommaso
Fix For: 2.1.0.BETA1
Attachments: SeamWebApplication.java
The Seam Wicket integration is very interesting. But currently the conversation
propagation is limited to form submit action and SeamLink component.
This limitation prevents to use it in a real world application where page navigation can
be implemented with several different components: button, link, submit link, ajax events.
Among all it would be really useful that the conversation propagation would be supported
by the AjaxEventBehavior component that implements Ajax interaction in Wicket and where it
is expected to bring the most important benefits (no more detached entities and
LazyInitializationException on loading proxyed objects).
Regards,
// Paolo Di Tommaso
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira