I am working on JBoss 3.2.5: when deploying a deployment unit, JBoss doesn't find a suitable deployer for, the JAR deployer is trying to deploy this unit. This can end up with a ZipException and the unit is listed as deployed with state 'STARTED'.
I suggested (with bug#996536) not to deploy unknown units. Ejort closed the bug with the reason "Your change would mean typos are unexpectedly ignored.", telling me to use the DeploymentFilter for units I don't want to have deployed. But this can be a problem. The guy doing our deployment can (unintended) deploy many units and I can't find any criteria making sense to configure the DeploymentFilter. My question: if JBoss tries to deploy everything not matching the configured criteria, shouldn't it be listed as FAILED when the JARDeployer (as "last-chance-deployer" ;-) couldn't deploy anything? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848148#3848148 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848148 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
