commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Pinet (JIRA)" <>
Subject [jira] Updated: (SANDBOX-256) Can not unregister a Compressor in CompressorFactory and an Archive in ArchiverFactory
Date Fri, 26 Sep 2008 02:23:44 GMT


Tim Pinet updated SANDBOX-256:

    Attachment: CompressorFactory.patch

I have implemented: 

> Can not unregister a Compressor in CompressorFactory and an Archive in ArchiverFactory
> --------------------------------------------------------------------------------------
>                 Key: SANDBOX-256
>                 URL:
>             Project: Commons Sandbox
>          Issue Type: Bug
>          Components: Compress
>         Environment: N/A
>            Reporter: Tim Pinet
>         Attachments: ArchiverFactory.patch, CompressorFactory.patch
>   Original Estimate: 10h
>  Remaining Estimate: 10h
> I am implementing my own Bzip2Compressor, ZipArchive, and TarArchive implementations.
I can create them and register them successfully but they will not be accessible via CompressorFactory.getInstance()
or ArchiveFactory.getInstance() due to the statically registered org.apache.commons.compress.archivers.tar.TarArchive
and for ArchiveFactory and org.apache.commons.compress.compressors.bzip2.BZip2Compressor
for CompressorFactory. The defaults will be returned since they are found in the list first.
There is no mechanism to unregister these statically registered defaults.
> It is recommended to implement:
> A) clearCompressorsList() or clearArchiversList() methods that will clear out the respective
lists, or
> B) implements an unregister(Class) method so that we can unregister specific archives/compressors.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message