The following jaas-service.xml is deployed fine: | [starksm@succubus lib]$ jar -tf client-login-tests.jar | META-INF/MANIFEST.MF | org/jboss/test/security/clientlogin/BeanA.class | org/jboss/test/security/clientlogin/BeanB.class | org/jboss/test/security/clientlogin/BeanC.class | org/jboss/test/security/clientlogin/IClientLogin.class | org/jboss/test/security/clientlogin/IClientLoginHome.class | jaas-service.xml | META-INF/ejb-jar.xml | META-INF/jboss.xml | because jaas-service.xml is a context with a null metadata location, hence itself matches the metadata file. Its the identification of the structure that determines which contexts are deployment candidates. The .bsh suffix needs to be added to the FileStructure in order for these scripts to be recognized as deployable: | <!-- File Structure --> | <bean name="FileStructure" class="org.jboss.deployers.vfs.plugins.structure.file.FileStructure"> | <!-- Unless specified the default list of suffixes is -service.xml, -beans.xml, -ds.xml, -aop.xml --> | <constructor> | <parameter> | <set elementClass="java.lang.String"> | <value>-service.xml</value> | <value>-beans.xml</value> | <value>-ds.xml</value> | <value>-aop.xml</value> | </set> | </parameter> | </constructor> | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113049#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...