There should be no need for such hardcoding. The problem with the old jar deployer was 1) There was no ordering of deployers when it did accepts() 2) It was first to recognise it wins 3) The deployers were loaded in an adhoc fashion
With the new deployers, the structural component that analyses the structure will be ordered (still with first to recognise it wins). Also, the structural deployers will be amongst the first things to be deployed. i.e. we don't have to worry about the jar deployer stealing a war deployment inside a sar because its sar was processed before the tomcat sar. The only way it is not going to work is if you don't have a war deployer. In that case, the jar deployer will be the only one that recognises the deployment. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862627#3862627 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862627 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
