Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Inspect Your Webapp in a Live Environment Interactively with GroovyConsole

DZone's Guide to

Inspect Your Webapp in a Live Environment Interactively with GroovyConsole

· Java Zone ·
Free Resource

Verify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!

Have you ever needed to check the state of your webapp’s objects/Session/.. to find out why the hell something doesn’t work or have you had to learn a weird 3rd party API that is only available on the server? Then you were doomed … until the publication of GroovyConsole. JeeUtils GroovyConsole provides a JSP page that let you execute any Groovy/Java code on the server side, with access to server-side objects like request/session etc.

Here is a screenshot of my recent troubleshooting session, where I needed to check the state of a session-scoped JSF Managed Bean:

(Notice that the screenshot uses heavily the beauties of Groovy though you could use the ordinary boring Java too :-) .)

The application is self-explanatory (and pretty small) so just check it check it out (and let me know what you think).

If you would prefer telnet access (and can have the port open) then you may be also interested in the Embedding Groovy article.

 

From http://theholyjava.wordpress.com/2011/09/27/inspect-your-webapp-in-a-live-environment-interactively-with-groovyconsole/

Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}