JBoss development,
A new message was posted in the thread "StructureModificationChecker and Synch with
VFS3":
http://community.jboss.org/message/518806#518806
Author : John Bailey
Profile :
http://community.jboss.org/people/johnbailey
Message:
--------------------------------------------------------------
One option for the profile service to guarantee to have a VFS pointer to the original file
is to mount the real filesystem pointing to the original file, but using a different VFS
mount point. So if you have an archive like test.jar, you could mount it into a special
VFS location managed by the profile service. This would allow the PS to always have a way
to access the original.
File test = new File(uriToTestFile);
VirtualFile psCopy =
VFS.getChild("/profileservice").getChild("test.jar");
VFS.mountReal(test, psCopy);
From that point on you can always get the original through psCopy
regardless of what mounting/over-mounting occurs during deployment.
This would help since there would then be no reason for the VFS or the deployers to try
and manage what the original really is.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/518806#518806