Default application configuration lost after undeploy and deploy back

[samsonsouley]

Environment Details

• GlassFish Version (7.0.6):
• JDK version: 17
• OS: Linux
• Database: Postgres

---

Problem Description

When i undeploy and and deploy back an application which was set earlier as default application i have to go back and set the application back as default

Steps to reproduce

• Deploy the web application
• Set the application as default application
• undeploy the application
• Deploy the application

Impact of Issue

After deploying back the application you will not be able to access the application if you do not precise the context name

[OndroMih]

This is actually a feature in GlassFish - if an application is undeployed, it's removed as the default web module: https://github.com/eclipse-ee4j/glassfish/blob/d322a5705f498a16210ceee9e6b7762a9cfa739c/appserver/admingui/common/src/main/java/org/glassfish/admingui/common/handlers/DeploymentHandler.java#L296

One way to implement support for keeping the default web module config between undeploy and deploy is to:

• change the removeFromDefaultWebModule in DeploymentHandler to indicate that the name of the removed web module should be remembered as the previous default web module, and the next deploy command would set the deployment as the default web module if the name is the same

Another option would be to keep the value of the default web module even if the application is undeployed. We would need to check whether this would break anything if there's a default web module set to a non-existing module (while the app is undeployed).