Currently we do not support multiple deployers for the same content so there cannot be 2 or more deployers that recognize the same deployment types. Work is underway to support a chain of deployers in the next gen server.
The DeploymentSorter defaults should still be used if the MainDeployer is not deployed using an xmbean descriptor, so there is no reason to remove the static defaults. Every deployer can express their deployment suffixes and relative order using the org.jboss.deployment.SubDeployerSupport Suffixes and RelativeOrder attributes. I think that proper configuration of all deployers to use this should resolve the JBAS-1517 issue. If not, point out what is lacking. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870963#3870963 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870963 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
