If you're running with log4j in your app, set the logging priority on
the root logger to debug. It spews a lot of messages, and the type
converter messages are there - I was using this facility the other day
when trying to upgrade an existing app from 2.0.x to 2.1.2.
Andy.
On 9 Jan 2009, at 09:12, Robert Graf-Waczenski wrote:
Hi!
To my knowledge, you have to enable devMode. This gives you a lot of
debugging output and exception stack traces on the console. The
drawback is that it makes your application rather sluggish.
Yes, the article you quote is well known. I agree, Struts2 sucks big
time in this regard while being an excellent framework otherwise.
Robert
Vincent Lin wrote:
Hi,
Is there anyway to get better error message there's an error
occurring in
ognl?
Everytime there's an exception in ognl it's swallowed.
And I ran into some "No Result Found for XxxAction" error.
It's extremely hard to debug, because there's no any useful
information in
it.
All of them seem to be converter related problem.
Is there anyway to make struts 2 easier to debug?
There's an article complaining about this issue:
http://raibledesigns.com/rd/entry/does_struts_2_suck
Thanks,
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
