"david.lloyd(a)jboss.com" wrote : | I think the best solution is to have predictable/repeatable names for VFS URLs. I don't think using a UUID is really useful in practice anyway. Why not allow a name to be assigned to vfsmemory URLs? Then one could simply put the appropriate vfsmemory URL in the security policy file. If security is a concern, one could simply introduce a permission that is necessary in order to create a vfsmemory URL with a given name. I'll enable this in InMemoryClassesDeployer, so the user can determine its own predictable/repeatable name. By default this will still be UUID, but I'll add some deployment unit based helpers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190958#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...