This content has been marked as final.
Show 3 replies
-
1. Re: Default VFS caching locations
alesj May 22, 2009 7:17 AM (in response to jaikiran)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 -
2. Re: Default VFS caching locations
jason.greene May 22, 2009 12:34 PM (in response to jaikiran)"alesj" wrote:
Or if the newly/additionally added "deploy" folder is not high volume,
does it still make sense to permanently cache it?
The problem is that the current deployers & VFS design is *very* dependent on permanent caching of VFS roots, per the discussion here:
http://lists.jboss.org/pipermail/jboss-development/2009-April/014187.html
So, anything which doesn't use it will eventually fail (unless they aren't using temps). -
3. Re: Default VFS caching locations
jaikiran May 25, 2009 4:04 AM (in response to jaikiran)"jason.greene@jboss.com" wrote:
(unless they aren't using temps).
And from what i remember, every deployment irrespective of how its packaged will be temped.