5 Replies Latest reply on Oct 17, 2004 2:31 PM by starksm64

    Deployment sorting

    pilhuhn

      At least in Branch_4_0_0, the .aop and *aop.xml files are not in the
      list of the DeploymentSorter.
      If I undestand a forum entry from Scott and Andy corretcly, then those should be deployed after deployer and before sar?

        • 1. Re: Change Notes: 3.2.4
          starksm64

          AbstractPasswordCredentialLoginModule.java

          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.

          • 2. Re: Deployment sorting
            starksm64

            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.

            • 3. Re: Deployment sorting
              pilhuhn

              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.

              Cheers
              Heiko

              • 4. Re: Deployment sorting
                bill.burke

                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?

                • 5. Re: Deployment sorting
                  pilhuhn

                  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 ;-/

                  Thanks
                  Heiko