I've got the following question: how an average application server makes its apps initialisation ? I've my own thoughts on the topic, but really looking for any specification even for a particular one application server, but had no success neither for Tomcat ( for example) nor for Glassfish.
More precisely: I need info about how AppServer understands that it has new app to launch, and how it really does that ( unzip jar/war/ear -> looks for specific class file at specific location, parses specific config files, adds libraries into its classpath.... ) Btw: classpath issue is very important one also - how application server decides on application classpath ( creates their own, or shares its own classpath with every launched application ).
It is all very easy when you just use AppServers for deploy, and run and maybe simple configuration. But when you would like to under how things really work, their implementation and what is happening under the hood - then interesting things appear. I have my own vision on how I would implement all interesting issues, but have some doubts about entire implementation in existing application servers.
If there are some links on the Internet - I would really appreciate.
Thank you for your time!
Aucun commentaire:
Enregistrer un commentaire