jboss-metadata:1.0.0.CR2 is invalid due to JBMETA-131. The issue is that some processors will need to be explicitly given a ClassLoader for the deployment, so I've defined JBMETA-132 to remove processing from JBoss50Creator and instead put this responsibility on the caller/consumer to create a ProcessorChain and run it. For AS this will be implemented as another deployer in the mix; I'm considering using this to start an EJB3 Deployers project. The JNDI Binding Policy Decorator Deployer would likely move here as well. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183102#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...