http://jira.jboss.com/jira/browse/JBRULES-575
I can't seem to manage to isolate the problem :/
It's not just because I have 2 different references to Team in Match
- because I wrote an integration test with Cheese and CheeseCouple that
worked.
See the issue for more info.
I am using
With kind regards,
Geoffrey De Smet
Edson Tirelli wrote:
Geoffrey,
My guess is that ShadowProxyFactory is failing to match a method that
is declared in a superclass or interface with the overriden method in a
subclass. Because of this, it is trying to proxy 2 times the same
method. I
Geoffrey, yes that does sound like a bug. The automatic proxy/scheduling is
quite new, and will take some time to stabilise - could you create a test
case and JIRA, and email me please (with the JIRA, so I make sure it is not
lost) ? I will then (with edson) take a look into it, as there will
Geoffrey,
Plz, if you can open a JIRA with a sample it would be great. Probably
some kind of unexpected method name conflict.
Regarding the feature, right now it is mandatory, but I was talking
to Mark to make it optional. Unfortunally Shadow Facts are one of those
necessary evils. If
@drools.codehaus.org
Subject: Re: [drools-user] [trunk] Repetitive field name/signature in class
Geoffrey, yes that does sound like a bug. The automatic proxy/scheduling is
quite new, and will take some time to stabilise - could you create a test
case and JIRA, and email me please (with the JIRA, so I make
I just tried the trunk (to compare a benchmark between it and the
branch), but I got an error, anything I can do about it?
Are shadow facts optional? (or are they better always anyway?)
java.lang.ClassFormatError: Repetitive field name/signature in class
file
If it isn't a known bug, I 'll happily make another testcase patch.
I am pretty sure it's because I have 2 different references to Team in
Match, namely homeTeam and awayTeam.
With kind regards,
Geoffrey De Smet
Geoffrey De Smet wrote:
I just tried the trunk (to compare a benchmark between
