Its magic

Bro, your compiled web archives were simply behind the code. Nothing magic about it, but I get it.

@CaptainRant what do you mean archives were behind the code?

@zemaits When you are developing a web application, it is hosted in a web container (such as Apache Tomcat, Jboss, Weblogic, etc), which communicates with a web server (Apache HTTP server, etc).

When you deploy the web application to verify functionality (besides tests), the container takes care of the life cycle of your code. It takes all of your code, compiles it, puts it into a web archive such as a .war or an .ear and then deploys that archive into the web container's listening directory, after which the web container picks it up and hosts it, for you to run your application.

Once that is done, you can run your application. Then, you decide to add more functionality to it by writing a new piece of code. You refresh the page and.. your code changes do not seem to have had effect.

The problem is that you forgot to deploy these changes back to the web container so that it could re-host the application archives to include your changes.

@CaptainRant Why they use these containers?

All I know is using a ftp and a shared webhosting to upload php websites.

@CaptainRant that's what I missed after switching from Apache + PHP to Azure + C#. In PHPStorm you could set it to auto-upload but C# needs building so upload on saving would suck ;-;

@zemaits So that we can save time and resources.

He agrees