-
1. Re: Going to pull the vfs packages into a separate project
starksm64 Dec 18, 2006 10:51 PM (in response to starksm64)The current mc/container/vfs trunk has been copied to a new maven project under:
https://svn.jboss.org/repos/jbossas/projects/vfs/trunk/
The tests run fine within eclipse, but when from from maven the vfsfile and vfsjar protocol handlers are not getting picked up for some reason. After testing against jboss-head I'll do a 2.0.4.snapshot release of this. -
2. Re: Going to pull the vfs packages into a separate project
starksm64 Dec 18, 2006 11:38 PM (in response to starksm64)With the latest vfs code, the server startup is 1m:43s while the code in the mc 2.0.0.Beta it starts in 13s.
-
3. Re: Going to pull the vfs packages into a separate project
starksm64 Dec 19, 2006 3:10 AM (in response to starksm64)The problem is hasBeenModified() causing trashing of the cache due to the first call always returning false. I have updated this method to not return true when cachedLastModified is uninitialized and the startup time is back down to 14s.
public boolean hasBeenModified() throws IOException { boolean hasBeenModified = false; long last = getLastModified(); if (cachedLastModified != last) { hasBeenModified = cachedLastModified != 0; cachedLastModified = last; } return hasBeenModified; }
I have created a 2.0.0.Beta2 release of the vfs. -
4. Re: Going to pull the vfs packages into a separate project
bill.burke Dec 19, 2006 7:24 AM (in response to starksm64)Sorry, I didn't get a chance to test this with a JBoss instance after I committed it. Was in the process of doing that which is why I didn't add it to the repository,
-
5. Re: Going to pull the vfs packages into a separate project
starksm64 Dec 19, 2006 4:17 PM (in response to starksm64)The vfs code has been removed from the mc trunk and replaced with references to the jboss-vfs.jar from thirdparty.