You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2008/04/06 12:07:25 UTC

[jira] Assigned: (WICKET-1476) Referencing Page may cause StackOverflowError

     [ https://issues.apache.org/jira/browse/WICKET-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Compagner reassigned WICKET-1476:
---------------------------------------

    Assignee: Johan Compagner

> Referencing Page may cause StackOverflowError
> ---------------------------------------------
>
>                 Key: WICKET-1476
>                 URL: https://issues.apache.org/jira/browse/WICKET-1476
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.2
>            Reporter: Gerolf Seitz
>            Assignee: Johan Compagner
>         Attachments: StackOverflowBug.zip
>
>
> scenario:
> + 2 pages. each page stores itself in the session in the constructor ( -> last accessed instance of a page is stored in session (which ultimately is rather bad in the first place))
> + have a final reference to session in page's constructor
> + access page 1 mounted as "first" (-> pageId=0)
> + access page 2 mounted as "second" several times so that new pages are created until page1 gets serialized
> + access the serialized page 1 via "/first.0"
> + StackOverflowError

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.