Remove the notification listener behavior as its useless to clear the
shared state map on a cf stop since only the login modules active during
authentication have access to it.
No, in the absence of an explict declaration of the order, an unknown deployment suffix will be deployed after all others. Note that in 4.0 the deployment suffixes can be set via the SuffixOrder attribute of the org.jboss.deployment.MainDeployer-xmbean.xml found in the conf/xmdesc directory.
Hm. ok. I did probably misworded my post.
I did not want to assume that the aop files get implicitly deployed between 'deployer' and 'sar'.
I wanted to ask if aop should not be added to either the DeploymentSorter or to the XMbean-DD you mentioned.
The way the AOP deployer works is that when jboss-aop.deployer is deployed, it inserts .aop and aop.xml into the MainDeployer suffix list.
ARe you having problems?
No, no problems - au contraire.
It wasn't obvious to be that it does this, and I apparently did not read enough of AspectDeployer.java ;-/