Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Subject: DO NOT REPLY [Bug 35750]  -
    Memory leak in JUnit task
Message-Id: <20050715104439.EDCE317@ajax.apache.org>
Date: Fri, 15 Jul 2005 12:44:39 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35750


------- Additional Comments From j_a_fernandez@yahoo.com  2005-07-15 12:44 -------
I am always thinking that is something wrong on all this lestener mechanisms 
that people build in Java. Most APIs have addListener and removeListener but 
there is no way to test if a listener is already there and if one tries to 
remove and is not there it throws exceptions at you. Which means you need to 
do bookkeeping on the side. And complicates code unnecessarily. 

I do not know if using week-references as the listeners will solve this kinds 
of issues of memory leaks, you still need to keep a hard reference somewhere 
so that the weak is not lost. Any ideas how to design better listeners/ this 
ANT problem is just an example.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org