[ https://issues.apache.org/jira/browse/WICKET-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506021 ]
Eelco Hillenius commented on WICKET-670: ---------------------------------------- Another alternative would be to put such a page in a separate project. If you include the project, you have the page. > Bring back the inspector! > ------------------------- > > Key: WICKET-670 > URL: https://issues.apache.org/jira/browse/WICKET-670 > Project: Wicket > Issue Type: Wish > Components: wicket > Affects Versions: 1.4.0-alpha > Reporter: Jonathan Locke > Priority: Minor > Fix For: 1.4.0-alpha > > > My copy of the inspector is completely broken. It's a shame that this useful > tool is not really supported anymore. It gives people a sense of confidence > when they can navigate their wicket session and see all the components with > the inspector. > To bring the inspector back, we could do the following things: > 1. fix the inspector > - it needs to factor out the stack trace metadata so sizes of things are > more accurate > - my inspector causes every page viewed after using it to fail with a page > expired exception (!) > 2. add a security setting setInspectorEnabled() which defaults to false > (disabled) and unless > the inspector is explicitly enabled, the constructor of every publicly > accessible bookmarkable > page in the inspector package throws an IllegalStateException() with an > explanation of what > you must do to safely use the inspector in your application (add security to > the pages via > wicket-auth-roles or some other means and call setInspectorEnabled(true)). > then we can all enjoy the return of the inspector! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.