I opened a jira https://issues.apache.org/jira/browse/GERONIMO-5636, and will do more investigation when have time, aslo, any comment is appriciated
If you mean to handle the unpacked archives and zip files on the fly, Geronimo has already done some abstraction, like the interface ResourceContext and some sub class of JarFile.
Will check the karaf deployer :-)
Another great feature is that, from the truezip document, it seems to suppot directly write/delete the jar file, not use the stream copy workaround.
2010/9/29 Guillaume Nodet <firstname.lastname@example.org>
I'd rather use a deployment which can handle unpacked archives and zip them on the fly.The karaf deployer supports that (if you're in Geronimo 3). It may even work with symlinks (not sure though) so you could link to the output of your build directly.
Just my 2 cents.--On Wed, Sep 29, 2010 at 10:40, Ivan <email@example.com> wrote:
While looking at the deployment codes, I was tired of packing/unpacking the application package, actually, what we do is just to add some Geronimo specific configuration files, updating some configuration files.
IIRC, in one deployment process, we need to
a. copy the jar file to a temp folder
b. extract the zip file
c. package the directory for the application analysis
d. repackage the directory for the final installation.
How about using the TrueZip, it is a ASL 2.0 opensource project, and seems it supports updating the zip file virtually, even the nested zip file.
Project URL : https://truezip.dev.java.net/
Any comment ? thanks.
Open Source SOA