[ http://issues.apache.org/jira/browse/WICKET-129?page=all ]
Martin Benda updated WICKET-129:
--------------------------------
Attachment: patch-2.0.diff
patch-1.x.diff
Patches for 2.0-SNAPSHOT (trunk) and 1.3-incubating-SNAPSHOT (wicket-1.x).
> WicketTester cannot test applications with custom WebRequestCycle
> -----------------------------------------------------------------
>
> Key: WICKET-129
> URL: http://issues.apache.org/jira/browse/WICKET-129
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.2.2, 1.2.3, 2.0, 1.3, 1.2.4
> Reporter: Martin Benda
> Attachments: patch-1.x.diff, patch-2.0.diff
>
>
> MockWebApplication class should use
> Session#getRequestCycleFactory#newRequestCycle(...) factory method to create
> new instances of WebRequestCycle instead of using WebRequestCycle's
> constructor directly. Otherwise, using the WicketTester to test a
> WebApplication that creates a custom WebRequestCycle (by overriding
> WebApplication#getRequestCycleFactory or Session#getRequestCycleFactory) wil
> probably fail.
> The attached patch replaces all occurences of "new WebRequestCycle(...)" with
> the factory method call.
> Regards,
> Bendis
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
