glassfish
  1. glassfish
  2. GLASSFISH-5267

Cannot see Context URL for .war in .ear

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 9.1peur2
    • Fix Version/s: future release
    • Component/s: deployment
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5,267

      Description

      Sometimes it happens that, due to several reasons, the administrator decides to
      bind a .war file to some particular Context URL. So he changes the Context URL
      found in the admin GUI for that .war.

      Unfortunately, when the .war is not standalone but part of an .ear file, the
      administrator does not see that Context URL. So he cannot change it.

        Activity

        Hide
        harpreet added a comment -

        Marking target milestone as 9.1.1

        Show
        harpreet added a comment - Marking target milestone as 9.1.1
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        mkarg added a comment -

        Increased priority to P3 according to
        https://glassfish.dev.java.net/public/IssueTrackerPriority.html. The ability to
        change the context URL is an essential feature for a lot of customers, so not
        being able to do that is a major usability issue. Also until now nobody filed a
        workaround in the comments list of this issue, so it seems there is no workaround.

        Show
        mkarg added a comment - Increased priority to P3 according to https://glassfish.dev.java.net/public/IssueTrackerPriority.html . The ability to change the context URL is an essential feature for a lot of customers, so not being able to do that is a major usability issue. Also until now nobody filed a workaround in the comments list of this issue, so it seems there is no workaround.
        Hide
        Anissa Lam added a comment -

        Admin Console is not designed to show context root of embedded war, and doesn't
        provide launching embedded war either.
        This is not a bug, but RFE. Marking as such.
        To do this, we need deployment backend to provide an API so that we can get the
        context root of embedded war. Currently this is not available.
        Transferring to "deployment". If this API is available, please reassign to GUI
        to finish the implementation.

        Show
        Anissa Lam added a comment - Admin Console is not designed to show context root of embedded war, and doesn't provide launching embedded war either. This is not a bug, but RFE. Marking as such. To do this, we need deployment backend to provide an API so that we can get the context root of embedded war. Currently this is not available. Transferring to "deployment". If this API is available, please reassign to GUI to finish the implementation.
        Hide
        Hong Zhang added a comment -

        Scrubbing RFEs for GlassFish 4.0.

        Show
        Hong Zhang added a comment - Scrubbing RFEs for GlassFish 4.0.
        Hide
        Jeremy_Lv added a comment -

        It seems like the issue about http://java.net/jira/browse/GLASSFISH-11710.

        Show
        Jeremy_Lv added a comment - It seems like the issue about http://java.net/jira/browse/GLASSFISH-11710 .
        Hide
        Hong Zhang added a comment -

        Currently only the context roots of the standalone modules are stored in the domain.xml, maybe we should make it consistent and store the context roots of the web modules which are part of the ear in the domain.xml also which could make this kind of editing possible. We can explore more about this in next release.

        Show
        Hong Zhang added a comment - Currently only the context roots of the standalone modules are stored in the domain.xml, maybe we should make it consistent and store the context roots of the web modules which are part of the ear in the domain.xml also which could make this kind of editing possible. We can explore more about this in next release.

          People

          • Assignee:
            Hong Zhang
            Reporter:
            mkarg
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: