PROTECTED]
Sent: Monday, 20 August 2007 1:57 PM
To: Struts Developers List
Subject: Re: Exception thrown in OGNL evaluation.
Hi, Rene,
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> > You won't get NPE in this scenario. Ognl automatically create
instance
> > for you. I believe yo
PROTECTED]
Sent: Monday, 20 August 2007 1:57 PM
To: Struts Developers List
Subject: Re: Exception thrown in OGNL evaluation.
Hi, Rene,
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> > You won't get NPE in this scenario. Ognl automatically create instance
> > for you.
Hi, Rene,
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> > You won't get NPE in this scenario. Ognl automatically create instance
> > for you. I believe you know about this feature.
> >
>
> Not when trying to read the property, only when applying values. The first
> invocation with null foo object
Am Fr, 17.08.2007, 11:28, schrieb Ruimo Uno:
> Rane,
>
> 2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
>> Ruimo,
>>
>> see below
>>
>> Ruimo Uno schrieb:
>> > Hi, thanks for your comment.
>> >
>> > 2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
>> >> It's no bug, it's a feature...
>> >>
>> >> The policy
Rane,
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> Ruimo,
>
> see below
>
> Ruimo Uno schrieb:
> > 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
> >> e
Ruimo,
see below
Ruimo Uno schrieb:
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 evaluat
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(),
