One issue I'm running into with the refactored structural deployer code is that a number of the unit tests expect that "top-level" deployments are accepted as valid. Both the JarStructure and FileStructure were accepting top-level directories (based on DeploymentContext.isTopLevel()) as valid without validating anything about the actual structure. Before trying to restore this behavior, I want to question this as a valid construct. Its essentially a mix of pre-determined structure with the root being marked as a valid deployment, but the children unknown. With the new structure deployment spi, such a deployment would have to have a StructureMetaData with a ContextInfo that corresponds to the valid root. With such a StructureMetaData, there is not much point in validating that the structure deployers recognize the VirtualFile for the root as valid since its declared to be so. I'll hack around it for now and come back to this if its causing other issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980472#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...