being new to Weblogic, I followed some readme files to deploy apps to Weblogic, by copying the war files to the autodeploy folder. They automatically showed in the Weblogic console, so far so good.
Later, I deleted some of these apps from the autodeploy folder, expecting them to also disappear from the Deployments page. To my surprise, once I started the server, they were still there, and I couldn't remove them either: Weblogic was saying that I needed to delete the wars from the autodeploy folder (!).
Of course, I should have read the documentation first, that states the following:
Auto-Deploying, Redeploying, and Undeploying Archived Applications
To auto-deploy an archived application, copy its archive file to the /autodeploy directory. WebLogic Server automatically sets the application’s deployment mode to stage mode.
A deployment unit that was auto-deployed can be dynamically redeployed while the server is running. To dynamically redeploy, copy the new version of the archive file over the existing file in the /autodeploy directory.
To undeploy an archived deployment unit that was auto-deployed, delete the application from the /autodeploy directory. WebLogic Server stops the application and removes it from the configuration. Note: If you delete an application from the /autodeploy directory when the server is not active, WebLogic Server will not detect that the application was deleted even when the server is again in an active state. In order to prevent an out-of-sync domain tree, BEA recommends that you only remove applications from the /autodeploy directory when the server is in an active state.
Since I've deleted the files while the server was down, they still show up there. What is not in this particular documentation is how to fix it once it's out-of-sync.