This is working in 'rough draft' at this point and coupled with the new programmatic deployment (JBAS-1425) goes a long way toward eliminating the XSL deployer all together. One 'hack' that I did put in was to set the JNDI name in the ManagedConnectionFactory on deployment. This makes resolving an entry in the repository much easier if multiple connection definitions exist in the repository (eg our JDBC adapters). I can't see anything necessarily wrong with doing this as it's simply a mechanism to avoid failing on a deployment when the RAR can't be guessed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010863#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...