[
https://issues.apache.org/jira/browse/SANDBOX-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Pinet closed SANDBOX-256.
-----------------------------
Resolution: Won't Fix
The issues that I posted pertain to the current trunk. I was just informed of
the new 'redesign' branch. I will close this issue and investigate the new
branch.
> Can not unregister a Compressor in CompressorFactory and an Archive in
> ArchiverFactory
> --------------------------------------------------------------------------------------
>
> Key: SANDBOX-256
> URL: https://issues.apache.org/jira/browse/SANDBOX-256
> 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
> org.apache.commons.compress.archivers.zip.ZipArchive 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.
