[jboss-dev-forums] [JBoss Microcontainer Development POJO Server] New message: "Re: StructureModificationChecker and Synch with VFS3"

[John Bailey]

JBoss development,

A new message was posted in the thread "StructureModificationChecker and Synch with VFS3":

http://community.jboss.org/message/518633#518633

Author  : John Bailey
Profile : http://community.jboss.org/people/johnbailey

Message:
--------------------------------------------------------------
Right.  The problem is the VFS is setup to show the current structure.  So archives that are unzipped and mounted will in essence hide the original archive.  To work around this we can create another VFS mount for the original file, but then anyone who needs to determine modifications would need to be aware if changes were made to the original.  So it will get ugly quick. 
 
Once really ugly example is what can occur with WAR deployments:
 
Ex.  /path/test.war
  1.  The original archive is mounted as a Zip archive creating a temporary location like /${jboss.temp.dir}/1-test.war
  2.  The temp location is mounted in the original VFS location
  3.  The WAR deployer invokes a deep copy of the archive to avoid file locking problems with creates another temp location /${jboss.temp.dir}/2-test.war
  4. The temp location is mounted in the original VFS location
 
The same path in VFS has represented three different OS filesystem locations.  The code checking for modifications needs to know the original archive file to check. It can't get it from the VFS without some implementation details being exposed.  By design the client view of the VFS only exposes the current state of the mounts, and if you want to know if something is modified, you will be checking the current structure regardless of what originally existed in various mount points.
 
Since the modifications being checked for are occurring on the original files, a lot of code and workarounds could be avoided by NOT using the VFS to check for modifications. 
 
Any thoughts?

--------------------------------------------------------------

To reply to this message visit the message page: http://community.jboss.org/message/518633#518633