"scott.stark(a)jboss.org" wrote : There is no requirements for vfs to be used for deployers. We have run into this with pure programatic deployments not having associated VirtualFiles. Sure, that's why I'm saying Deployment(Context) should hold that methods. It's just that we currently know how to impl that on top of VFS. e.g. for plain Deployment(Context) it could either be noop or simple defaults (true to exists, false to isModifed). And I don't see how names like exists(), isModified() cannot be used for any kind of deployment. In this case, this would just make your profile even more basic, at least on modification level. That you map deployment against vfs/uri that's your impl detail. But part of that profile could be then used any where. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156376#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...