I can look into that too. One option I guess is to load the jar into a byte array and have pointers into that array for the entries, returning BAIS, when needed. This seems like a memory hog though as you have to have the contents of the Jar in memory. I wonder if JarFile and the URLClassLoaders that use them are efficient in that regard? Using a stream interface so that they don't have to keep the raw bytes in memory. If not, then the bytearray approach probably works great.
I think thats sorta what you're already doing with the current implementation that is there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990160#3990160
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990160