[JBoss Microcontainer Development POJO Server] New message: "VFSClassloaderPolicy and VFS3 Mounting"
by John Bailey
JBoss development,
A new message was posted in the thread "VFSClassloaderPolicy and VFS3 Mounting":
http://community.jboss.org/message/518774#518774
Author : John Bailey
Profile : http://community.jboss.org/people/johnbailey
Message:
--------------------------------------------------------------
Below is a discussion Ales and I had over email....
John:
>
> Mainly, when a VFSClassLoaderPolicy is created outside the deployer
> framework (ex. JMXKernel), how do we make sure the archives are
> mounted and who is responsible for their cleanup? Right now there is
> a hack that will ensure the archives are mounted, but will leak the
> reference to the mount. In this case it seems like the creator of
> the policy should really be responsible for the handling of the
> references, and the policy should not be aware. Any thoughts?
Ales:
> Currently VFSCLPolicy can be created two ways:
> (a) from deployers
> (b) from <classloader> element
>
> For (a) we should already taken care of its archives via structural deployers.
> With (b) policy is created via bean which is a Module which creates the policy.
> So, in that case, I would just add create and destroy methods to this Module bean, where we would mount and unmount via bean's lifecycle callbacks.
>
> For any other usage the user should be aware of how to properly use VFS3.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/518774#518774
15 years
[JBoss Microcontainer Development POJO Server] New message: "Re: StructureModificationChecker and Synch with VFS3"
by Emanuel Muckenhuber
JBoss development,
A new message was posted in the thread "StructureModificationChecker and Synch with VFS3":
http://community.jboss.org/message/518723#518723
Author : Emanuel Muckenhuber
Profile : http://community.jboss.org/people/emuckenhuber
Message:
--------------------------------------------------------------
Hmm yeah this is where the problems with VFS2 started. In the end ProfileService does not know what the deployers are internally doing with the VirtualFile and it actually should not need to know. However not using VFS to do modification checks seems to just move the workarounds to somewhere else.
In general ProfileService only needs the orignal/unmounted view. There is no need to access the contents of a zip or temp files - therefore it makes sense that there is no auto-mounting done at this level.
The ModificationChecker was originally part of ProfileService and would rather belong there. Although i'm not really sure about the temp sync part though. Since the farming service needs something like this it might could be part of this as well. For now it does not really matter where the ModificationChecker is located, but there should be a way to access the actual VirtualFile which was used to create the VFSDeployment in the first place.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/518723#518723
15 years