You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/08/26 02:27:18 UTC
[jira] Resolved: (WICKET-2010) InspectorPage doesn't show component
tree
[ https://issues.apache.org/jira/browse/WICKET-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2010.
-----------------------------------
Assignee: Igor Vaynberg (was: Jeremy Thomerson)
Fix Version/s: 1.4.11
1.5-M2
Resolution: Fixed
> InspectorPage doesn't show component tree
> -----------------------------------------
>
> Key: WICKET-2010
> URL: https://issues.apache.org/jira/browse/WICKET-2010
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.4-RC1
> Reporter: Juergen Donnerstag
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.11, 1.5-M2
>
>
> public InspectorPage(final PageParameters parameters)
> {
> add(new ApplicationView("application", Application.get()));
> add(new SessionView("session", Session.get()));
> IPageMapEntry entry = null;
> try
> {
> entry = getPageMap().getEntry(parameters.getInt("pageId"));
> }
> entry seems always to return null, thus the list of components is never shown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.