Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
Yep. Contrary to the old OM handling the new one demands equals()
method properly implemented for
all objects put on OM.
Is it something bad?
I have no idea :) why such requirement?
Because stack implementation used to maintain local scopes uses some variation
of ListArray class
that uses equals() when remove() method is called. Just for efficiency I guess
that real scope could
be implemented and need for proper equals() implementation would be eliminated
but I think it's
minor issue.
Question is why is my entity
Contractor equalized to javascript NativeObject?
Most probably because you are having some NativeObjects produced by flow put on
OM. That's enough to
obtain such effect. Anyway, it is valid to call equals() with object of
different class passed as
parameter. In such case, equals() should return false before trying to cast.
Yeah I know that but why isn't the NativeObject unwrapped for comparison?
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
