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

["Johan Compagner (JIRA)" <ji...@apache.org>]

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

Johan Compagner closed WICKET-1476.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.4

the example could be even a bit simpler
The problem was that when pages where references in Component (metadata) or MarkupContainter (childs)
then the page readObject isnt yet called to register the page as being read in.
Moved to Component now so that it is in the lowest wicket class.

> 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
>             Fix For: 1.3.4
>
>         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.