[GLASSFISH-5267] Cannot see Context URL for .war in .ear Created: 07/Jul/08  Updated: 16/Apr/13

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: 9.1peur2
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 5,267


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.

Comment by harpreet [ 04/Sep/08 ]

Marking target milestone as 9.1.1

Comment by sanandal [ 11/Jan/09 ]

"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."

Comment by mkarg [ 27/Apr/09 ]

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.

Comment by Anissa Lam [ 22/Sep/09 ]

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.

Comment by Hong Zhang [ 10/Oct/12 ]

Scrubbing RFEs for GlassFish 4.0.

Comment by Jeremy_Lv [ 15/Apr/13 ]

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

Comment by Hong Zhang [ 16/Apr/13 ]

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.

Generated at Thu Dec 08 12:28:15 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.