It's doable, but it have doubts over if it's soon enough.
I can check if the PS has some nice/transparent way of adding this to VFSCache's
permanent roots.
The issue also might be that the actual cache impl might not be the one that has permanent
roots.
Or if the newly/additionally added "deploy" folder is not high volume,
does it still make sense to permanently cache it?
I guess something that is scanned by PS,
should be able to define which kind of vfs cache it would like to use,
then it's up to the actual impl if it can provide that.
The problem that I see with this is that the vfs cache should be user transparent,
but perhaps not at that level, only higher up, e.g. when dealing with URLs, VirtualFiles,
etc
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232692#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...