Folks.
Proxy/Shadow should be optional...there are a number of scenarios where it
kills performance.....
Going further, it maybe should be made optional at Object Type Level.

  _____  

From: Michael Neale [mailto:[EMAIL PROTECTED] 
Sent: sexta-feira, 1 de dezembro de 2006 09:20
To: user@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 sure it is not
lost) ? I will then (with edson) take a look into it, as there will have to
be changes to the ASM code that generates the proxy no doubt. I am not sure
if proxy/shadowing will be optional or not - haven't been tracking progress
with that (in any case it should be transparent to you) - Mark or Edson can
fill in on the details for that for 3.2. 

Michael.


On 11/30/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: 

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 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 net/sf/taseree/samples/travelingtournament/domain/MatchShadowProxy
>
>
> Here's my Match class:
>
> public class Match extends AbstractPersistable implements
> Comparable<Match>, Solution {
>
>     private Team homeTeam;
>     private Team awayTeam;
>
>     private Day day; 
>
>     // getters, setters, clone(), toString()
>
> }
>
> AbstractPersistable has a Long id with getters/setters
>


--------------------------------------------------------------------- 
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email




Reply via email to