I have a patch that will throw a runtime exception when either(iff
'struts.el.throwExceptionOnFailure' is true):
* Property is not found
* Method is not found
* An exception is thrown from the expression evaluation
It seems to work fairly well, but I am sure it will need more tweaking
and lots of
The OgnlValueStack swallows the exceptions. Always rethrowing the
exception is not an option, as that it not wanted in many places. The
challenge is to do some refactoring, so the exceptions are thrown only
when OgnlValueStack:find(...) is called from the view. I will play
around with it, see if I
>
> I agree, Struts2 sucks big time in
> this regard while being an excellent framework otherwise.
>
> Robert
Judging from my (not very long) experience with Struts2, I agree wholeheartedly
with that.
It really seems badly broken that the framework (OGNL, in this case)
swallows exceptions (even i
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, a
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
5 matches
Mail list logo
