Hi, thanks for your comment.
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> It's no bug, it's a feature...
>
> The policy for model access (e.g. property calls) via expression
> evaluation is fail silent. It would cause tons of exceptions if ognl
> expression evaluation / property access would not
It's no bug, it's a feature...
The policy for model access (e.g. property calls) via expression
evaluation is fail silent. It would cause tons of exceptions if ognl
expression evaluation / property access would not swallow them.
The business logic access methods of your action, such as prepare(),
Hi,
I have submitted this to user list a few hours ago but finally, I
found the root cause of this issue. So, here I report it to dev list.
If an exception is thrown while OGNL expression evaluation such as in
the following scenario:
XXXAction
public String getMessage() {
throw new Nu
yes
On 8/16/07, Nils-Helge Garli <[EMAIL PROTECTED]> wrote:
> I've started to get these as well...Probably get one now when I submit
> this one Do the emails still go through (guess I'll know if
> someones answer)?
>
> Nils-H
>
> On 8/15/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> > I
I've started to get these as well...Probably get one now when I submit
this one Do the emails still go through (guess I'll know if
someones answer)?
Nils-H
On 8/15/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> I always get it. I never thought I would spam myself :)
>
> musachy
>
> On 8
