Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46FAD491.3050004@apache.org>
Date: Wed, 26 Sep 2007 23:52:17 +0200
From: Grzegorz Kossakowski <gkossakowski@apache.org>
User-Agent: Thunderbird 2.0.0.5 (X11/20070719)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: ObjectModel exception
References: <46F7BED6.9010700@mobilebox.pl> <46F9662B.3060000@apache.org>
 <46FABAA0.2030804@mobilebox.pl> <46FABC36.3010209@apache.org>
 <46FAC7FF.6030005@mobilebox.pl>
In-Reply-To: <46FAC7FF.6030005@mobilebox.pl>
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit

Leszek Gawron pisze:
> Grzegorz Kossakowski wrote:
>> Leszek Gawron pisze:
>>
>> 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.
>>
>>
>> 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?

Because comparison is made by low-level class like ArrayList that is unaware of wrapping objects.

Do you want to say that NativeObjects should be unwrapped always whenever they are used in Java code?

This can be done easily in o.a.c.components.flow.FlowHelper.setContextObject() but I must be sure
that this will not introduce another problems.

-- 
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/