Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 88572 invoked from network); 3 Feb 2003 18:02:04 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Feb 2003 18:02:04 -0000 Received: (qmail 25569 invoked by uid 50); 3 Feb 2003 18:03:35 -0000 Date: 3 Feb 2003 18:03:34 -0000 Message-ID: <20030203180334.25568.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: ant-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 16726] New: - External FilterReaders don't get chain()ed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16726 External FilterReaders don't get chain()ed Summary: External FilterReaders don't get chain()ed Product: Ant Version: 1.5.1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Core AssignedTo: ant-dev@jakarta.apache.org ReportedBy: didge@foundrylogic.com External FilterReaders that are specified using never have their chain() method called, even if they impelement the ChainableReader interface. It appears that using to load a filter reader creates an instance of AntFilterReader. Unfortunately, ChainReaderHelper.getAssembledReader() forces re-instantiation of AntFilterReader's target filter reader's class each time it is called. One fix would be to have AntFilterReader cache the instantiated target filter reader instancce, if the target reader is an instance of ChainableReader, so that its chain method could be called.