[
https://issues.apache.org/jira/browse/WICKET-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634575#action_12634575
]
Igor Vaynberg commented on WICKET-1845:
---------------------------------------
a bit more detail, the problem is timing. the browser can request topframepage
before the session cookie is set. therefor requests for bottomframepage and
topframepage can happen in two different sessions. this is what cause the wrong
page to be resolved - it was being pulled out of the wrong session.
furthermore, the frameset markup should be changed to something like this:
<frameset rows="25%, 75%">
<frame noresize="noresize" frameborder="1"
src="/myproject/topframe/wicket:pageMapName/topframe/">
</frame>
<frame noresize="noresize" frameborder="1"
src="/myproject/bottomframe/wicket:pageMapName/bottomframe/">
</frame>
</frameset>
it is a good idea to keep pages from different frames in different pagemaps.
> WicketRuntimeException when using wicket-auth-roles in a frameset
> -----------------------------------------------------------------
>
> Key: WICKET-1845
> URL: https://issues.apache.org/jira/browse/WICKET-1845
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-auth-roles
> Affects Versions: 1.3.4
> Environment: Windows XP, WebSphere 6.1
> Reporter: Steve Hiller
> Assignee: Matej Knopp
> Priority: Minor
> Attachments: myproject.zip, pom.xml, stacktrace.txt
>
>
> Hi All,
> I seem to have a very strange exception when using wicket-auth-roles in a
> frameset.
> Let me try and sketch out the setup:
> 1) Application home page is called FramesetPage.java
> -- it extends org.apache.wicket.markup.html.WebPage
> -- corresponding HTML contains simple frameset with 2 rows
> 2) Top row of frameset contains TopFramePage.java
> -- it extends org.apache.wicket.markup.html.WebPage
> -- corresponding HTML contains only an image component as follows:
> -- add(new Image("bannerImage", "logo.png"));
> 3) Bottom row of frameset contains BottomFramePage.java
> -- it extends org.apache.wicket.markup.html.WebPage
> -- it requires authentication/authorization using wicket-auth-roles (as
> is, straight out of the jar)
> -- if not already authenticated/authorized then redirected to
> MySignInPage.java
> -- it extends
> org.apache.wicket.authentication.pages.SignInPage
> -- corresponding HTML contains standard <span
> wicket:id="signInPanel"/> tag
>
> Here's the strange part: After completing the 'Username' and 'Password'
> fields of the
> signInPanel then the exception displayed in the attached stack trace is
> thrown. Further, if I replace the image
> component in TopFramePage with some CSS that loads the same image then no
> exception is thrown.
> Any thoughts on what is causing this problem?
> Thanks,
> Steve
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
