Console

Console Project

Wicket Console provides support for executing code dynamically (at runtime). The main goal is to provide capabilities to inspect, debug and modify state and behavior of the application during development and testing.

Using Wicket Console is as easy as simply adding GroovyScriptEnginePanel to a page. This panel consists of a simple form to input Groovy code, execute it and see the output and return value. Besides that, there is a ClojureScriptEnginePanel to run Clojure code and additional tables to easily copy pre defined script templates to the input area. For examples with source code see http://wicketconsole.appspot.com.

Here's a list of possible applications of Wicket Console:

• Clear Wicket's markup and properties caches at runtime
• Read/Modify the state of any component of your system at runtime
• Execute and evaluate Hibernate HQL or Hibernate queries
• Enable logging (e.g. Hibernate SQL statements) at runtime
• Enable Hibernate statistics at runtime
• Clear caches
• Inspect the component hierarchy
• Get the session or component tree size
• Read system properties

There's basically no limitation in what you can do. So keep in mind, though, that with great power comes great responsibility. Think twice before using this in a production environment and to which user to give access to Wicket Console.

Wicket Console currently supports Groovy and Clojure.