> No in fact it is the contrary my pet idea was the directory names > first/second/third this is what the class in London decided was the simplest > to use (as opposed to going and setting mbean names left and right which is > the direction you are heading full speed).
My 2 cents: For users who need this sort of behaviour, I think it would be nice, but I wouldn't want to force it down the throats of all users. Perhaps, deploy first any URLs whose names match the ordered deployment naming convention, then deploy everything else as it is done now. Was this what you had in mind? If this is the case, then I believe the naming scheme should be more mangled than just xxx1.jar, yyy2.ear, ... This could very easily be done on accident by unwary users (ex. myApp_ver3.jar). Perhaps force the name to be xxx_jborder_1.jar, or something else unlikely to be duplicated on accident. Also, I think that if a user does specify a particular ordering within the Scanners MBean config, then that should take precedence over anything else. -Larry _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
