You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Roy van Rijn (JIRA)" <ji...@apache.org> on 2007/08/24 15:07:31 UTC
[jira] Commented: (WICKET-851) WicketTester unusable after
subsequent startPage(Page) call
[ https://issues.apache.org/jira/browse/WICKET-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522504 ]
Roy van Rijn commented on WICKET-851:
-------------------------------------
That sounds more like a workaround (?)
Although using startPage(Class) works, IMHO it is not right the framework throws an exception when you call startPage(Page) subsequently.
Could I get a second opinion on this?
btw. I'm not trying to bug you guys, just trying to make a better framework, don't get me wrong.
> 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.