ample), when null, it's not throws NullPointerException, but
>> "org.mvel.PropertyAccessException: unable to resolve property".
>> With that, I never imagined that the problem was nullPointer, but I
>> thought about any access visibility (duh!).
>>
>> []'s
>> Alessa
MyFact( $value : value )
> eval( $value.before(DateHelper.getModifiedDate(-6, "MONTHS")))
>
> The use of a non-time-constant inline eval (or return value
> predicates)
> causes unpredictable behavior in the engine.
>
> []s
> Edson
>
>
> 2008/5/7
ng to this board as I seem to have junked the thread up a bit lol
>
>
> Michael B. escreveu:
>> Okay, I wrote a test case around the following and it works fine so let
>> me
>> know if this isnt what you are working with...
>>
>> Foo C
I dont know if this is still outstanding since the original post seems to
have disappeared, but this is what I did during my proof of concept that I
am going through:
In a helper class (i.e. DateHelper) I had this method:
public static Date getModifiedDate(int amount, String unit) {
el.CompileException: unable to resolve property: name
> Caused by: org.mvel.PropertyAccessException: unable to resolve
> property:name
>
>
>
>
> Michael B. escreveu:
>
> According to your error it appears you had a typo somewhere. The error
> you
> pasted in was looking for the
Okay, I wrote a test case around the following and it works fine so let me
know if this isnt what you are working with...
Foo Class
public class Foo {
private String m_name;
public String getName()
{
return m_name;
}
public void setName(String n
According to your error it appears you had a typo somewhere. The error you
pasted in was looking for the property nome instead of name.
Alessandro Lazarotti wrote:
>
> If I've the simple classes:
>
> public class ObjectBar{ public String name; gets/sets}
>
> public class ObjectFoo{ public
