You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Federico Fanton (JIRA)" <ji...@apache.org> on 2008/04/21 17:51:21 UTC

[jira] Created: (WICKET-1558) WicketTester.startPage(page) throws "No requestCycle is currently set"

WicketTester.startPage(page) throws "No requestCycle is currently set"
----------------------------------------------------------------------

                 Key: WICKET-1558
                 URL: https://issues.apache.org/jira/browse/WICKET-1558
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.3.3
         Environment: Eclipse 3.3.1.1 on Ubuntu 7.10
            Reporter: Federico Fanton
            Priority: Minor


I'm receiving a strange message with WicketTester in 1.3.3.. Whenever I use startPage(Page) I get a

"there was an error cleaning up target org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget@1465464107[Page class = org.apache.wicket.util.tester.DummyHomePage, id = 1, version = 0]->testPage->interface org.apache.wicket.markup.html.link.ILinkListener.ILinkListener (request paramaters: [RequestParameters  componentPath=1:testPage pageMapName=null versionNumber=0 interfaceName=ILinkListener componentId=null behaviorId=null urlDepth=-1 parameters={} onlyProcessIfPathActive=false])."

followed by

"No requestcycle is currently set!"

To reproduce, just use a QuickStart with a completely static Homepage.html (no wicket:id's) and an empty Homepage.class (just a "Homepage extends WebPage"), while the test itself is

new WicketTester().startPage(new HomePage());

with

log4j.logger.org.apache.wicket=DEBUG

inside log4j.properties, to enable logging.

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


[jira] Commented: (WICKET-1558) WicketTester.startPage(page) throws "No requestCycle is currently set"

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604507#action_12604507 ] 

Martin Grigorov commented on WICKET-1558:
-----------------------------------------

Just for the history: using wicketTester.clickLink(String, true) (i.e. AJAX request) will detach the RequestCycle at the end of the call and thus it will be 'null' from now on.

This is valid for Wicket 1.3.2.

> WicketTester.startPage(page) throws "No requestCycle is currently set"
> ----------------------------------------------------------------------
>
>                 Key: WICKET-1558
>                 URL: https://issues.apache.org/jira/browse/WICKET-1558
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>         Environment: Eclipse 3.3.1.1 on Ubuntu 7.10
>            Reporter: Federico Fanton
>            Assignee: Maurice Marrink
>            Priority: Minor
>             Fix For: 1.3.4
>
>         Attachments: testreqcycle.zip
>
>
> I'm receiving a strange message with WicketTester in 1.3.3.. Whenever I use startPage(Page) I get a
> "there was an error cleaning up target org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget@1465464107[Page class = org.apache.wicket.util.tester.DummyHomePage, id = 1, version = 0]->testPage->interface org.apache.wicket.markup.html.link.ILinkListener.ILinkListener (request paramaters: [RequestParameters  componentPath=1:testPage pageMapName=null versionNumber=0 interfaceName=ILinkListener componentId=null behaviorId=null urlDepth=-1 parameters={} onlyProcessIfPathActive=false])."
> followed by
> "No requestcycle is currently set!"
> To reproduce, just use a QuickStart with a completely static Homepage.html (no wicket:id's) and an empty Homepage.class (just a "Homepage extends WebPage"), while the test itself is
> new WicketTester().startPage(new HomePage());
> with
> log4j.logger.org.apache.wicket=DEBUG
> inside log4j.properties, to enable logging.

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


[jira] Updated: (WICKET-1558) WicketTester.startPage(page) throws "No requestCycle is currently set"

Posted by "Federico Fanton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Federico Fanton updated WICKET-1558:
------------------------------------

    Attachment: testreqcycle.zip

Quickstart (Eclipse project)
Testcase is it.ibc.Test

> WicketTester.startPage(page) throws "No requestCycle is currently set"
> ----------------------------------------------------------------------
>
>                 Key: WICKET-1558
>                 URL: https://issues.apache.org/jira/browse/WICKET-1558
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>         Environment: Eclipse 3.3.1.1 on Ubuntu 7.10
>            Reporter: Federico Fanton
>            Priority: Minor
>         Attachments: testreqcycle.zip
>
>
> I'm receiving a strange message with WicketTester in 1.3.3.. Whenever I use startPage(Page) I get a
> "there was an error cleaning up target org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget@1465464107[Page class = org.apache.wicket.util.tester.DummyHomePage, id = 1, version = 0]->testPage->interface org.apache.wicket.markup.html.link.ILinkListener.ILinkListener (request paramaters: [RequestParameters  componentPath=1:testPage pageMapName=null versionNumber=0 interfaceName=ILinkListener componentId=null behaviorId=null urlDepth=-1 parameters={} onlyProcessIfPathActive=false])."
> followed by
> "No requestcycle is currently set!"
> To reproduce, just use a QuickStart with a completely static Homepage.html (no wicket:id's) and an empty Homepage.class (just a "Homepage extends WebPage"), while the test itself is
> new WicketTester().startPage(new HomePage());
> with
> log4j.logger.org.apache.wicket=DEBUG
> inside log4j.properties, to enable logging.

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


[jira] Updated: (WICKET-1558) WicketTester.startPage(page) throws "No requestCycle is currently set"

Posted by "Johan Compagner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Compagner updated WICKET-1558:
------------------------------------

    Fix Version/s: 1.3.4
         Assignee: Maurice Marrink

> WicketTester.startPage(page) throws "No requestCycle is currently set"
> ----------------------------------------------------------------------
>
>                 Key: WICKET-1558
>                 URL: https://issues.apache.org/jira/browse/WICKET-1558
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>         Environment: Eclipse 3.3.1.1 on Ubuntu 7.10
>            Reporter: Federico Fanton
>            Assignee: Maurice Marrink
>            Priority: Minor
>             Fix For: 1.3.4
>
>         Attachments: testreqcycle.zip
>
>
> I'm receiving a strange message with WicketTester in 1.3.3.. Whenever I use startPage(Page) I get a
> "there was an error cleaning up target org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget@1465464107[Page class = org.apache.wicket.util.tester.DummyHomePage, id = 1, version = 0]->testPage->interface org.apache.wicket.markup.html.link.ILinkListener.ILinkListener (request paramaters: [RequestParameters  componentPath=1:testPage pageMapName=null versionNumber=0 interfaceName=ILinkListener componentId=null behaviorId=null urlDepth=-1 parameters={} onlyProcessIfPathActive=false])."
> followed by
> "No requestcycle is currently set!"
> To reproduce, just use a QuickStart with a completely static Homepage.html (no wicket:id's) and an empty Homepage.class (just a "Homepage extends WebPage"), while the test itself is
> new WicketTester().startPage(new HomePage());
> with
> log4j.logger.org.apache.wicket=DEBUG
> inside log4j.properties, to enable logging.

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


[jira] Resolved: (WICKET-1558) WicketTester.startPage(page) throws "No requestCycle is currently set"

Posted by "Maurice Marrink (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maurice Marrink resolved WICKET-1558.
-------------------------------------

    Resolution: Fixed

Verified with 1.3.3, however the wicket 1.3 branch does not have this problem anymore (1.3.4). Nor does trunk (1.4-m2)

> WicketTester.startPage(page) throws "No requestCycle is currently set"
> ----------------------------------------------------------------------
>
>                 Key: WICKET-1558
>                 URL: https://issues.apache.org/jira/browse/WICKET-1558
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>         Environment: Eclipse 3.3.1.1 on Ubuntu 7.10
>            Reporter: Federico Fanton
>            Assignee: Maurice Marrink
>            Priority: Minor
>             Fix For: 1.3.4
>
>         Attachments: testreqcycle.zip
>
>
> I'm receiving a strange message with WicketTester in 1.3.3.. Whenever I use startPage(Page) I get a
> "there was an error cleaning up target org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget@1465464107[Page class = org.apache.wicket.util.tester.DummyHomePage, id = 1, version = 0]->testPage->interface org.apache.wicket.markup.html.link.ILinkListener.ILinkListener (request paramaters: [RequestParameters  componentPath=1:testPage pageMapName=null versionNumber=0 interfaceName=ILinkListener componentId=null behaviorId=null urlDepth=-1 parameters={} onlyProcessIfPathActive=false])."
> followed by
> "No requestcycle is currently set!"
> To reproduce, just use a QuickStart with a completely static Homepage.html (no wicket:id's) and an empty Homepage.class (just a "Homepage extends WebPage"), while the test itself is
> new WicketTester().startPage(new HomePage());
> with
> log4j.logger.org.apache.wicket=DEBUG
> inside log4j.properties, to enable logging.

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