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

Posted to commits@wicket.apache.org by "Edvard Fonsell (JIRA)" <ji...@apache.org> on 2013/06/04 11:02:19 UTC

[jira] [Created] (WICKET-5215) Better exception message when Page instantiation fails in DefaultPageFactory

Edvard Fonsell created WICKET-5215:
--------------------------------------

             Summary: Better exception message when Page instantiation fails in DefaultPageFactory
                 Key: WICKET-5215
                 URL: https://issues.apache.org/jira/browse/WICKET-5215
             Project: Wicket
          Issue Type: Improvement
          Components: wicket
    Affects Versions: 6.8.0
            Reporter: Edvard Fonsell
            Priority: Minor


If injecting dependencies to a page fails in DefaultPageFactory.newPage, the exception message is a bit misleading:

"Can't instantiate page using constructor '...' and argument '...'. Might be it doesn't exist, may be it is not visible (public)."

It could also mention the possibility of failing to inject the dependencies, which seems to be the case in many occasions.

Even better, when calling the constructor fails, it could check the existence and visibility of the constructor instead of guessing what was the problem.

--
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