You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (Created) (JIRA)" <ji...@apache.org> on 2012/02/03 13:25:53 UTC
[jira] [Created] (WICKET-4384) cleaning up PageParameters in
AbstractBookmarkableMapper returns an empty instance if no parameters are
left after sanitizing instead of 'null' which by wicket definition
indicates that we have no page parameters
cleaning up PageParameters in AbstractBookmarkableMapper returns an empty instance if no parameters are left after sanitizing instead of 'null' which by wicket definition indicates that we have no page parameters
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WICKET-4384
URL: https://issues.apache.org/jira/browse/WICKET-4384
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.5.4, 6.0.0
Reporter: Peter Ertl
Assignee: Peter Ertl
^ see summary
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4384) improve wicket's handling of empty /
null page parameters
Posted by "Peter Ertl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-4384:
-------------------------------
Description: - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters (was: - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
- DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters)
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4384) improve wicket's handling of empty
/ null page parameters
Posted by "Peter Ertl (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl resolved WICKET-4384.
--------------------------------
Resolution: Fixed
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4384) improve wicket's handling of empty /
null page parameters
Posted by "Peter Ertl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-4384:
-------------------------------
Description:
- after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
- DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
was:after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
Summary: improve wicket's handling of empty / null page parameters (was: cleaning up PageParameters in AbstractBookmarkableMapper returns an empty instance if no parameters are left after sanitizing instead of 'null' which by wicket definition indicates that we have no page parameters)
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4384) improve wicket's handling of empty
/ null page parameters
Posted by "Peter Ertl (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl resolved WICKET-4384.
--------------------------------
Resolution: Fixed
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4384) improve wicket's handling of empty /
null page parameters
Posted by "Peter Ertl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-4384:
-------------------------------
Comment: was deleted
(was: fixed in trunk)
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4384) cleaning up PageParameters in
AbstractBookmarkableMapper returns an empty instance if no parameters are
left after sanitizing instead of 'null' which by wicket definition
indicates that we have no page parameters
Posted by "Peter Ertl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-4384:
-------------------------------
Description: after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null' (was: ^ see summary)
> cleaning up PageParameters in AbstractBookmarkableMapper returns an empty instance if no parameters are left after sanitizing instead of 'null' which by wicket definition indicates that we have no page parameters
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
>
> after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4384) cleaning up PageParameters in
AbstractBookmarkableMapper returns an empty instance if no parameters are
left after sanitizing instead of 'null' which by wicket definition
indicates that we have no page parameters
Posted by "Peter Ertl (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl resolved WICKET-4384.
--------------------------------
Resolution: Fixed
Fix Version/s: 6.0.0
1.5.5
fixed in trunk
> cleaning up PageParameters in AbstractBookmarkableMapper returns an empty instance if no parameters are left after sanitizing instead of 'null' which by wicket definition indicates that we have no page parameters
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (WICKET-4384) improve wicket's handling of empty
/ null page parameters
Posted by "Peter Ertl (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl reopened WICKET-4384:
--------------------------------
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (WICKET-4384) improve wicket's handling of empty
/ null page parameters
Posted by "Peter Ertl (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl reopened WICKET-4384:
--------------------------------
> improve wicket's handling of empty / null page parameters
> ---------------------------------------------------------
>
> Key: WICKET-4384
> URL: https://issues.apache.org/jira/browse/WICKET-4384
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.4, 6.0.0
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Fix For: 1.5.5, 6.0.0
>
>
> - after calling cleanPageParameters() an empty set of page parameters is returned as an empty PageParameters instance when in fact it should be 'null'
> - DefaultPageFactory#newPage() should be sure to not pass 'null' to a page constructor with page parameters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira