[
https://issues.apache.org/jira/browse/DELTASPIKE-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950281#comment-16950281
]
ASF subversion and git services commented on DELTASPIKE-1390:
-------------------------------------------------------------
Commit cdc155ef3042ec93bce3574eef78e9d78eaecbad in deltaspike's branch
refs/heads/master from Christian Beikov
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=cdc155e ]
DELTASPIKE-1390 - Fix CLIENTWINDOW mode to work with frames
> Client window handler doesn't work with frames
> ----------------------------------------------
>
> Key: DELTASPIKE-1390
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1390
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JSF-Module
> Reporter: Christian Beikov
> Priority: Major
> Fix For: 1.9.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The CLIENTWINDOW handler code loses the window when frames are involved.
> Using e.g. a window scoped bean with the Primefaces Dialog Framework will
> result in issues. The bean is initialized in window1. A click on a button
> opens a dialog, which is opened through an iframe, but the dialog doesn't use
> the window id defined in the parent window. If a button in the dialog
> requires the original bean, it will find an uninitialized bean, because the
> frame gets a new window id window2.
> The solution is to use the root window for the window id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
