"dimitris(a)jboss.org" wrote : Ales is telling me this is not only a VFS issue;
the deployers will have to be changed as well. I don't know what exactly is required
for that, but if we don't go that direction I feel we are just going cyrcles with this
problem.
No, deployers already have this. ;-)
I was just trying to explain it to you, that I've made a little fix to handle this the
right way - adding new VFSUtils api and a new ModificationType enum in deployers.
I now diff between unpack (meant for nested archives only) and explode (mostly meant for
top level archives, but could be used on nested as well == then it's the same as
unpack).
Why I want to diff the two - we should already be able to handle (read, scan, ...) top
levels, so I don't really see the need to unpack them, except if you explicitly say
so, and that is what I call explode.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155994#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...