You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "bernard (JIRA)" <ji...@apache.org> on 2013/01/25 23:47:13 UTC

[jira] [Created] (WICKET-5008) PageProvider#getPageInstance() calls wrong Page Constructor if pageParameters is null

bernard created WICKET-5008:
-------------------------------

             Summary: PageProvider#getPageInstance() calls wrong Page Constructor if pageParameters is null
                 Key: WICKET-5008
                 URL: https://issues.apache.org/jira/browse/WICKET-5008
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 6.4.0
            Reporter: bernard


I was wondering why my pages' default constructors aren't called anymore since after 1.4.

The problem is that PageProvider#getPageInstance() does not distinguish between pages that have parameters and pages that don't.

This creates a messy situation for pages that accept page parameters.

One case I know of is ListenerInterfaceRequestHandler#respond() which calls ListenerInterfaceRequestHandler#getPage().

If this call hits an expired page then the page crashes in the constructor Page(final PageParameters parameters) because of the bogus parameters.

I would expect that the default constructor is called in this case.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira