Jim Ma [http://community.jboss.org/people/jim.ma] replied to the discussion "CXF jms integration" To view the discussion, visit: http://community.jboss.org/message/541296#541296 -------------------------------------------------------------- Sorry , I may do not explain this problem well . We now create SPI endpoint from ServletMetaData in web.xml . How to distinguish the jms tranport endpoint and create jms endpoint/MD from the user provided jbossws-cxf.xml like :   <jaxws:endpoint id='HttpHelloService'          implementor='org.jboss.test.ws.jaxws.samples.HelloImpl>      </jaxws:endpoint>                <!--jms endpoint->             <jaxws:endpoint id='JMSHelloService'             wsdlLocation="./wsdl/jms-samples.wsdl"                    implementor='org.jboss.test.ws.jaxws.samples.HelloImpl>      </jaxws:endpoint> AFAIK, the hornetq deployers create BeanMetaData for queue/topic deployment descriptor and KernalDeploymentDeployer will start/stop these BeanMetaData represents queue/topic created by hornetq deployers. I understood your suggestion : use deployer input to put the JMS DA after the deployer deployed jms destination.  In AS5 , we should put JMSDA after the last real stage deployer ServiceDeployer . AS6, we put JMSDA after KernalDeploymentDeployer. IOW, we do not rely on AS deployer frameworks' deployment dependency mechinism , we rely on the deployer order to resolve the deployment dependency. If this is acceptable and if you do not see any other problems , I will follow your suggestion (as your pseudocode shows) to rewrite . -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/541296#541296] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]