see why Drools cannot see proxy objects
> as equal. The only way I can think of is that there is some sort of
> direct object/class type check in Drools that's causing it not to
> realize that two objects are equal. But I could be wrong, and I hope
> I'm wrong. :)
>
> -C
is is
> not ideal as that means I need to basically create a duplicate POJO
> object to store all of the hibernate domain objects. No good.
>
> oh well, back to my a.id == b.id. :)
>
> -Chris
>
>
> On May 4, 2009, at 1:29 PM, Guto wrote:
>
>> Tha
ressed with drools, but if
> you're under a deadline... :)
>
> --- On Mon, 5/4/09, Guto wrote:
>
>> From: Guto
>> Subject: Re: [rules-users] Hibernate proxy objects equality tests
>> failing in Drools 5
>> To: "Rules Users List"
>> Date: Monday
bernate from jpa.
2) Kill the proxies and make them simple objects (not hibernate derivated).
3) don´t know, but i´m been realy in a deadline here.
again
thanks for anyone in advance !
--
Guto Maia
Consultor de TI / Desenvolvedor
CSM - SCJP- SCWCD - SCBCD - ZCE
> In fact, i´m really
;> unfortunelly i'm not
>> sure if it will solve my problem.
>>
>> Does anyone else uses Drools with objects that came from an
>> hibernate,
>> (proxies)?
>>
>> Also, i'm not using any proxy to fetch lazy data inside
>> my Drools
>>
d.
I'm using EJB3 + JPA (hibernate provider) and Drools 4 GA;
thanks in advance for any help
--
Guto Maia
CSM - SCJP- SCWCD - SCBCD - ZCE
Chris,
When you use "==" in a DRL field constraint (not eval), drools always
translates it into an .equals() call.
Having said that, there
