This is not a compilation error, it's a runtime error. It means
you're passing a wrong type.
For instance, you may do:
f.m(x)
where method m is declared to take a type T, but you pass an object x
of type S which is not a subtype of T.
To debug this, examine the arguments in the section of code.
Also, insert statements such as:
if (!(x instanceof T))
System.err.println(....)
before the call to f or use asserts.
- Godmar
On Fri, Jul 18, 2008 at 10:57 AM, Edson Tirelli <tirelli(a)post.com> wrote:
Hey John, I know it is difficult, but we need some way to reproduce...
can you isolate a few rules and run them in a loop trying to force the
exception?
2008/7/17 John Squire <jc_squire(a)hotmail.com>:
>
> Hi All,
>
> We are intermittently getting mvel compilation errors with the following:
>
> Caused by: java.lang.IllegalArgumentException: object is not an instance
> of declaring class
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.mvel.optimizers.impl.refl.MethodAccessor.getValue(MethodAccessor.java:61)
> ... 148 more
>
> The rules compile ok and the application will run normally (rules
> processing successfully) for a few days then this error will occur. Tried to
> replicate but once the application is restarted the last action before the
> failure is repeated and always processes successfully.
>
> Any help would be appreciated.
>
> Regards
> JS
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
--
Edson Tirelli
JBoss Drools Core Development
JBoss, a division of Red Hat @
www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users