[jbossws-issues] [JBoss JIRA] Created: (JBWS-2336) Fix JSE deployers ordering

Fix JSE deployers ordering -------------------------- Key: JBWS-2336 URL: https://jira.jboss.org/jira/browse/JBWS-2336 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 Adrian says: The relative order parameter only applies when the deployers have similar input/outputs. It's there for when you have multiple "filter"s. i.e. a deployer that has the same input/output type and you need to control the order in which the filters run (you should try to design away such a requirement if possible). e.g. VFSClassLoaderClassPathDeployer is a filter it inputs and outputs ClassLoadingMetaData. So does the ClassLoadingDefaultDeployer. 1) Webservices org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerPreJSE org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerPostJSE Currently the ordering of these is pretty weak. i.e. there is no guarantee the PRE will run before the POST, except that the relative order of PRE is -1 compared with Tomcat and the POST must run after Tomcat. This is very brittle to changes in the Tomcat Deployer which might move it earlier in the chain due to changes in its requirements. i.e. The TomcatDeployer takes some additional metadata beyond JBossWebMetaData. Shouldn't the PRE deployer also output JBossWebMetaData to show it modifies or process it and therefore MUST run before Tomcat? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira