The current behavior only exists because deployers are inserted into the front of the deployer list, and then queried in order. This should probably be ordered based on the suffix ordering available from the SubDeployerExt. getEnhancedSuffixes such that deployers with conflicting suffixes are ordered based on the suffix priority. The EJB3Deployer does not support this interface due to the attempts to run it in earlier server versions.
There needs to be a testcase to validate that one can added a deployer and take priority over accepting deployments for which a deployer already exists. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, December 29, 2005 8:31 PM To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] EJB3 dependency on deployer ordering I just implemented being able to deploy ejb3 archives in a .jar. To make this work, I have to guarantee that the EJB3 deployer runs accepts() before the old EJB2.1 deployer. It seems, whoever is added to the MainDeployer last, runs first when accepts is called. So, I added an EJBDeployer dependency to the EJB3Deployer. SO DON'T CHANGE THIS BEHAVIOR IN BRANCH 4.0 PLEASE!!!!!!!!!!!!!!!! -- Bill Burke Chief Architect JBoss Inc. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
