[jira] Issue Comment Edited: (WICKET-851) WicketTester unusable after subsequent startPage(Page) call

["Jean-Baptiste Quenot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522496 ] 

jbq edited comment on WICKET-851 at 8/24/07 6:01 AM:
----------------------------------------------------------------------

Use startPage(Class) or create your instances of Page within a request cycle (tester.createRequestCycle()), as creating a page ensures that a page map is stored in a session attribute.

      was (Author: jbq):
    Use startPage(Class) or create your instances of Page within a request cycle (tester.createRequestCycle()), as creating a page involves setting a session attribute unless you're using stateless pages.
  
> WicketTester unusable after subsequent startPage(Page) call
> -----------------------------------------------------------
>
>                 Key: WICKET-851
>                 URL: https://issues.apache.org/jira/browse/WICKET-851
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta2
>            Reporter: Roy van Rijn
>            Assignee: Jean-Baptiste Quenot
>            Priority: Minor
>             Fix For: 1.3.0-beta4
>
>         Attachments: wickettestertestfailure.patch
>
>
> When adding two unit-tests to the WicketTesterTest for issue WICKET-848 I ran into the following problem (see patch).

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