ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16726] New: - External FilterReaders don't get chain()ed
Date Mon, 03 Feb 2003 18:03:34 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16726>.
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 <filterreader> never have their 
chain() method called, even if they impelement the ChainableReader interface.

It appears that using <filterchain> 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.

Mime
View raw message