[
https://issues.apache.org/jira/browse/WICKET-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724505#action_12724505
]
Andrzej Michalec commented on WICKET-2092:
------------------------------------------
Will this fix go to 1.3.x as backport? I am not sure if 1.3.7 release is
planned, if so it would preserve anyone else problems. I cannot upgrade to 1.4
due to other deps... and yes, I have local workaround using registered own page
factory but someone may be bound to 1.3.x same way as I am.
cheers, andy.
> SignInPanel IllegalArgumentException exception
> ----------------------------------------------
>
> Key: WICKET-2092
> URL: https://issues.apache.org/jira/browse/WICKET-2092
> Project: Wicket
> Issue Type: Bug
> Components: wicket-auth-roles
> Affects Versions: 1.3.5, 1.4-RC1
> Reporter: Juri Prokofiev
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.4-RC3
>
>
> If HomePage don't have a default constructor there seems to be a problem with
> SignInPanel -- after the form submission an exception occured:
> java.lang.IllegalArgumentException: wrong number of arguments.
> The following code in DefaultPageFactory class might be bogus:
> if (argument != null)
> return (Page)constructor.newInstance(new Object[] { argument });
> else
> return (Page)constructor.newInstance(new Object[] {});
> Quickfix for solving the problem - replace "(PageParameters)null" with "new
> PageParameters()":
> setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(getApplication().getHomePage(),
> new PageParameters()));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
