We have different behavior on unknown archives vs. their exploded representation - e.g. the deployers testsuite for Not(Unpacked)ClientDeploymentUnitTestCase. NotClientDeploymentUnitTestCase (client1-not.ajar) is only recognized by FileStructure, so no further structure details are known. Where the NotUnpackedClientDeploymentUnitTestCase (dir unpacked-client1-not.ajar) is recognized by JARStructure and as such eventually pushed to Ejb3ClientDeployer. But this deployer requires only .jar names: | private String getDeploymentJndiName(DeploymentUnit unit) | { | String jndiName; | String shortName = unit.getSimpleName(); | if(shortName.endsWith(".jar/")) | jndiName = shortName.substring(0, shortName.length() - 5); | else if(shortName.endsWith(".jar")) | jndiName = shortName.substring(0, shortName.length() - 4); | else | throw new IllegalStateException("Expected either '.jar' or '.jar/' at the end of " + shortName); | | return jndiName; | } | So, in the first case we get empty DeploymentUnit - no children, where the second one is treated as client-app, but fails. This example (excluding the failure) is a general behavior, and I don't think the user expects its deployments to behave differently, whether they are packed or unpacked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110555#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...