From: <dim...@jb...> - 2005-09-11 22:55:25
|
I've made/tested the changes we discussed. - added a SubDeployerExt/SubDeployerExtMBean that has the additional EnhancedSuffixes attribute, to be used by the MainDeployer when implemented to retrieve suffix/order. - all deployers define and externalize their default EnhancedSuffixes (except for the ClientDeployer) - there is no hard-coded config in SuffxOrderHelper. - MainDeployer-xmbean.xml defines the following "static" sequence: 250:.rar,300:-ds.xml,400:.jar,500:.war,600:.wsr,650:.ear,800:.bsh,900:.last - the rest is build dynamically as deployer are registered: 050:.deployer,050:-deployer.xml,100:.aop,100:-aop.xml,150:.sar,150:-service.xml,200:.beans,250:.rar,300:-ds.xml,350:.har,400:.jar,450:.ejb3,450:.par,500:.war,600:.wsr,650:.ear,700:.jar,750:.zip,800:.bsh,900:.last - I guessed a relative order for the new .bean deployer, just after the .sar deployer - in most cases SubDeployer.accepts() can do the job, based on the configured EnhancedSuffix I've left the MainDeployer defining "static" suffixes that are not changed by the SubDeployers. Changing the logic to the complete opposite is something I would like to give some more thought. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3894118#3894118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3894118 |