[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4281) Conversations are not propagated to modal windows

[Norman Richards (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Richards updated JBSEAM-4281:
------------------------------------

    Fix Version/s: The future
                       (was: 2.2.1.CR1)


> Conversations are not propagated to modal windows
> -------------------------------------------------
>
>                 Key: JBSEAM-4281
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4281
>             Project: Seam
>          Issue Type: Bug
>          Components: Wicket
>    Affects Versions: 2.2.0.CR1
>            Reporter: Clint Popetz
>            Assignee: Clint Popetz
>             Fix For: The future
>
>
> Wicket does not use its own RequestCycleProcessor.respond when showing a ModalWindow, so the seam/wicket integration mechanism that propagates conversations doesn't propagate them to modal windows.
> A workaround is to create the modal window with an anonymous subclass that puts the conversation id in the javascript that is appended for opening the window:
> 	    add(modalWindow = new ModalWindow("yourModalTitle") { 
> 	    	protected AppendingStringBuffer postProcessSettings(AppendingStringBuffer settings) {
> 	    		return settings.replace(0, Integer.MAX_VALUE, 
> 	    				settings.toString().replaceFirst("(settings.src=\"[^\"]+)\"", "$1&cid=" + org.jboss.seam.core.Manager.instance().getCurrentConversationId()+'"'));
> 	    	}
> 	    });

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira