4 Replies Latest reply on Nov 1, 2004 4:14 PM by ericmolitor

    ROOT.war location

    ericmolitor
    ericmolitor Nov 1, 2004 10:36 AM

      Dug around on the JBossWeb (this) forum (searching for ROOT.war) but didn't find anything more detailed.

      What's the rational with putting ROOT.war in the jbossweb-*.sar exploded SAR? From a packaging point of view I guess its makes sense (guarantees its only deployed if the tomcat service is installed, etc), however from a deployment/user point of view it seems that this would be more appropriate to be in default (where all user deployable wars would go.)

      Possibly its done to deliniate the built in WAR from the user deployed WARS, however if this rational applies then whats with all the built in SAR's in deploy? etc, etc, etc...

      My opinion (of debatable merit) is that if this were moved to the deploy directory it would be more intuitive to end users. (Or is there a massive assumption that's missing why ROOT.war is in the jbossweb exploded SAR)

      • 29399 Views
      • Tags:
        • 1. Re: ROOT.war location
          anil.saldhana
          anil.saldhana Nov 1, 2004 11:14 AM (in response to ericmolitor)

          A Sar file can contain jars, wars etc. JBoss has integrated tomcat with its own sar file. Why should the ROOT.war be outside this sar file? If you want to remove tomcat, just remove this sar file.

          I think you should do more digging into documentation about what a SAR is, what exploded archives mean etc..... If you already know them, I apologize.

          Bottom line: It is far better for a service to contain all the configuration/apps etc within, than have them scattered around.

            • Actions
          • 2. Re: ROOT.war location
            starksm64
            starksm64 Nov 1, 2004 11:48 AM (in response to ericmolitor)

            There is no strong argument for the ROOT.war being in the sar other than its integrating with some of the tomcat content. The downside is that if you want to override the root context deployment it can be confusing where the existing root context war is coming from.

              • Actions
            • 3. Re: ROOT.war location
              ericmolitor
              ericmolitor Nov 1, 2004 4:13 PM (in response to ericmolitor)

              I'm aware of what a SAR is and can contain (no apology needed, I wasn't as clear as I could have been.) The reason I bring it up is that conceptually the ROOT.war should work under JETTY, Tomcat, Resin, or just about any other servlet container that is used. And it seems like if it were under deploy fewer users would be confused by it. (Albeit there is a strong argument to just RTFM and figure it out.) Just my two cents.

                • Actions
              • 4. Re: ROOT.war location
                ericmolitor
                ericmolitor Nov 1, 2004 4:14 PM (in response to ericmolitor)

                True, I forgot that ROOT.war references the Tomcat status servlet.

                  • Actions