[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Deployment cleanup & modifications

[adrian@jboss.org]

Why are you trying to "destroy" the Deployment object?

That is a client side object. That is supposed to be under the caller's control you shouldn't
be modifying it or giving it some "stateful" representation.

All the book keeping for temp data of a VFS file should be inside the VFS itself.
I said this before WRT to the horrible explicit VFS Cache you did, but I was ignored.

The "simplist" solution to this problem should be that when somebody creates a root
VFSContext it is against that object that the "temp" information should be stored
or at least linked.

That root VFSContext should always be "live" while somebody holds a
link to the root VirtualFile.

Then when somebody asks to cleanup a VirtualFile within that context, it can workout
which parts of the temp information need to be removed.

The context should still be usable, its just removed the temp data which would need to be
reconstructed. Which is why close() or destroy() is a bad name/semantic.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205553#4205553

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205553