4 Replies Latest reply on Apr 11, 2006 12:08 AM by asack

    Ear deployment ordering and Extension-Name/Extension-List

    bwallis42


      Am I correct in believing that setting the Extension-Name value in one ear file's MANIFEST.MF and including that same name in the Extension-List value in another ear file's MANIFEST.MF should cause the first ear file to be deployed before the second one?

      I'm sure I had this working once before but now it doesn't seem to be. I am running on JBoss 3.2.3.

      thanks.

        • 1. Re: Ear deployment ordering and Extension-Name/Extension-Lis
          starksm64

          No, this is not correct. A manifest reference should have no deployment impacts.

          • 2. Re: Ear deployment ordering and Extension-Name/Extension-Lis
            asack

            Isn't Extension-Name and Extension-List mechanisms really meant on a per JAR basis not EAR?

            I could be wrong but the examples in the spec are geared on a per module basis (check Chap 8).

            Though, I really believe intra-EAR dependencies should definitely be addressed in the next rev of J2EE (I sent my comments in, thanks Scott for the suggestion).

            • 3. Re: Ear deployment ordering and Extension-Name/Extension-Lis
              bwallis42

              Isn't the contents of "Extension-List" a list of the other extensions that a jar uses?

              Is there no way to define inter ear dependencies? I know I can use a prefix deployment sorter but that is so clunky, I have to rename all the ears/jars/*.xmls when they deployed to get them deployed in the right order.

              I did write a deployment sorter of my own that had a file containing a list of the deployments in the correct order but having to manage a central list of applications is a source of errors when there are multiple applications and developers.

              I was hoping to find a better way to do this.

              • 4. Re: Ear deployment ordering and Extension-Name/Extension-Lis
                asack

                 

                "bwallis42" wrote:
                Isn't the contents of "Extension-List" a list of the other extensions that a jar uses?

                Is there no way to define inter ear dependencies? I know I can use a prefix deployment sorter but that is so clunky, I have to rename all the ears/jars/*.xmls when they deployed to get them deployed in the right order.

                I did write a deployment sorter of my own that had a file containing a list of the deployments in the correct order but having to manage a central list of applications is a source of errors when there are multiple applications and developers.

                I was hoping to find a better way to do this.


                When you find one, let me know...I think this is a big defiency in the current J2EE 5 spec. Intra-EAR dependencies should be standardized. I have this same problem right now and the only solution I see is to use the PrefixSorter which is JBoss specific (kinda clunky if you ask me).

                I would like to see an application.xml section or some kind of EAR MANIFEST entry that allows me to specify a dependency which will be honored at deployment time.