11:10 a.m.
Hi,
I have the following MVEL expression in a rule (with drools 5.1.0M1):
Scenario( id == 6147 )
Scenario is an interface which has the following accessor (and tons of
other methods):
public interface Scenario
{
...
public int getId();
...
}
But either in Eclipse or when compiling the rules I get the following
error:
Unable to create Field Extractor for 'id' of '[ClassObjectType
class=com.daysofwonder.mm.Scenario]'
I tried tons of variants including:
Scenario( getId == 6147 )
that still doesn't work.
The only variant I could make work is:
$s : Scenario( )
Scenario ( eval($s.getId() == 6147 ) )
which is plain ugly.
using something else than a Scenario or defining a new interface with
only getId() in it makes it work.
Any idea about what I got wrong?
How can I debug the situation?
Thanks,
--
Brice Figureau
My Blog: http://www.masterzen.fr/
1:03 p.m.
Hi Brice,
You are doing it right:
Scenario( id == 6147 )
We've been through quite some changes in trunk, and because of that
there were some regressions that are being fixed as we speak. I suggest that
you either use the stable 5.0.1 for now or if you can wait till M2, it
should fix this kind of issue.
Edson
2010/2/3 Brice Figureau
<brice+drools@daysofwonder.com<brice%2Bdrools(a)daysofwonder.com
> Hi,
> I have the following MVEL expression in a rule (with
drools 5.1.0M1):
> Scenario( id == 6147 )
> Scenario is an interface which has the following accessor
(and tons of
> other methods):
> public interface Scenario
> {
> ...
> public int getId();
> ...
> }
> But either in Eclipse or when compiling the rules I get
the following
> error:
> Unable to create Field Extractor for 'id' of '[ClassObjectType
> class=com.daysofwonder.mm.Scenario]'
> I tried tons of variants including:
> Scenario( getId == 6147 )
> that still doesn't work.
> The only variant I could make work is:
> $s : Scenario( )
> Scenario ( eval($s.getId() == 6147 ) )
> which is plain ugly.
> using something else than a Scenario or defining a new
interface with
> only getId() in it makes it work.
> Any idea about what I got wrong?
> How can I debug the situation?
> Thanks,
> --
> Brice Figureau
> My Blog: http://www.masterzen.fr/
> _______________________________________________
> 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 by Red Hat @ www.jboss.com
2:25 a.m.
Hi,
On Wed, 2010-02-03 at 14:03 -0500, Edson Tirelli wrote:
Hi Brice,
You are doing it right:
Scenario( id == 6147 )
We've been through quite some changes in trunk, and because of
that there were some regressions that are being fixed as we speak. I
suggest that you either use the stable 5.0.1 for now or if you can
wait till M2, it should fix this kind of issue.
I will use the stable version for the moment and will upgrade when M2 is
available. I'll try to produce a test case for this problem if that can
be of any help.
Thanks for the answer!
--
Brice Figureau
My Blog: http://www.masterzen.fr/
4:11 a.m.
On Thu, 2010-02-04 at 09:25 +0100, Brice Figureau wrote:
Hi,
On Wed, 2010-02-03 at 14:03 -0500, Edson Tirelli wrote:
>
> Hi Brice,
>
> You are doing it right:
>
> Scenario( id == 6147 )
>
> We've been through quite some changes in trunk, and because of
> that there were some regressions that are being fixed as we speak. I
> suggest that you either use the stable 5.0.1 for now or if you can
> wait till M2, it should fix this kind of issue.
I will use the stable version for the moment and will upgrade when M2 is
available. I'll try to produce a test case for this problem if that can
be of any help.
It looks like the problem also happens with the 5.0.1 version :-(
--
Brice Figureau
My Blog: http://www.masterzen.fr/
3:04 p.m.
Ok, this one was hidden for a long time. Interesting no one stumbled on
it before you.
https://jira.jboss.org/jira/browse/JBRULES-2424
The problem is triggered in case your fact class/interface has a method
that matches the following 3 conditions:
* it is public
* its name starts with "set"
* it has no parameters
Your fact interface had a method:
public XXX setup();
That would make the ClassFieldInspector class to raise an exception,
making it impossible to create any field accessors for it.
Anyway, it is fixed now on trunk (to be released in M2) and branch
5.0.x. Meanwhile, the possible workaround is to break one of the three
conditions above: either make the method non-public, or rename it to not
start with "set" or add at least one (dummy) parameter to it.
Thanks for reporting.
Edson
2010/2/4 Brice Figureau
<brice+drools@daysofwonder.com<brice%2Bdrools(a)daysofwonder.com
> On Thu, 2010-02-04 at 09:25 +0100, Brice Figureau wrote:
> > Hi,
> > > On Wed, 2010-02-03 at 14:03 -0500, Edson Tirelli
wrote:
> > > > > Hi Brice,
> > > > > You are doing it
right:
> > > > > Scenario( id == 6147
)
> > > > > We've been
through quite some changes in trunk, and because of
> > > that there were some regressions that are being fixed as we speak. I
> > > suggest that you either use the stable 5.0.1 for now or if you can
> > > wait till M2, it should fix this kind of issue.
> > > I will use the stable version for the moment and will
upgrade when M2 is
> > available. I'll try to produce a test case for this problem if that can
> > be of any help.
> It looks like the problem also happens with the 5.0.1
version :-(
> --
> Brice Figureau
> My Blog: http://www.masterzen.fr/
> _______________________________________________
> 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 by Red Hat @ www.jboss.com
2:26 a.m.
Hi,
On Thu, 2010-02-04 at 16:04 -0500, Edson Tirelli wrote:
Ok, this one was hidden for a long time. Interesting no one
stumbled on it before you.
https://jira.jboss.org/jira/browse/JBRULES-2424
The problem is triggered in case your fact class/interface has a
method that matches the following 3 conditions:
* it is public
* its name starts with "set"
* it has no parameters
Your fact interface had a method:
public XXX setup();
That would make the ClassFieldInspector class to raise an
exception, making it impossible to create any field accessors for it.
I can understand why.
Anyway, it is fixed now on trunk (to be released in M2) and
branch
5.0.x. Meanwhile, the possible workaround is to break one of the three
conditions above: either make the method non-public, or rename it to
not start with "set" or add at least one (dummy) parameter to it.
Thanks for reporting.
Thank you for fixing it!
I renamed the method and it is now working!
--
Brice Figureau
My Blog: http://www.masterzen.fr/
5903
days inactive
5905
days old
5 comments
2 participants
participants (2)
-
Brice Figureau -
Edson Tirelli