Thanks Riyad.
Yes. The more we share what works, the more chance of finding what we need somewhere like in these forums.
When you say “most default out-of-box experience”, I don’t get that that works for developers.
What you provide us with is an IDE, which contains a debugger. I invite you to reconsider the notion of what a debugger is.
I propose that a powerful debugger is a tool that gives you the fastest route to finding why something didn’t work.
So, if I were developing the struts code, then a Java source level debugger would be useful. However, if I’m developing Struts-based solutions, especially if I’m only restructuring by making changes to struts-config.xml and to JSP pages, the Java debugger is going to be of little use for me.
I that case, my “debugger” is having the struts.action package showing me what’s happening.
I think that a log4j configurator as part of MyEclipse would be awesome, you could turn on/off debug levels from the package tree 😀
Do you get where we’re coming from here ? Maybe the thing is not so much struts, as giving really quick and direct access to logging for all Web apps.
Many thanks.
Neale