[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-362) Separate Archive API from what's needed by the underlying storage mechanism

Separate Archive API from what's needed by the underlying storage mechanism --------------------------------------------------------------------------- Key: SHRINKWRAP-362 URL: https://issues.jboss.org/browse/SHRINKWRAP-362 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Currently "Archive" is implemented by both ArchiveBase and ContainerBase. In truth, "Archive" is for the end-user view, and ArchiveBase is really used to centralize functions specific to doing underlying data storage. Separate these out such that ArchiveBase/MemoryMapArchive/MemoryMapArchiveImpl have a sane structure which clearly is centered around the operations necessary for ShrinkWrap's VFS, and don't abuse the Archive (end-user view) contract for these aims. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira