The JARDeployer won't accept jar files that contain .xml files in the META-INF directory, assuming this is a deployment for other deployers (e.g. EJBDeployer).

This is true if the deployment is unpacked and it is the expected behaviour (I believe).

But if the deployment is packed, the whole META-INF/ subtree is traversed (not just the immediate children files) so any nested .xml will cause the un-acceptance of the deployment.