A history lesson of deployment strategies
By vbkraemer on Jan 30, 2006
Folk who have been paying attention may note that the GlassFish Project is based on code that was originally part of SJSAS 8, so the article has information that is relevant today...
For example, folks who want to use a "supported" fast deployment method for their J2EE components and application may want to consider combining "Directory Deployment" with "Dynamic Reloading".
I have done some tests with dynamic reloading in the past. The reloading mechanism was smart enough to detect whether I had changed a DD file or a class and http://imdb.com/title/tt0097216/.
If you are an ant user, you can even write code that will detect if you have just changed a java file and do next to nothing when you build and "redeploy" a web app that just has JSP changes. [For JSP changes, you don't need to touch the dot-reload file...]
I haven't done it for a while, so I may need to look it up or reinvent it.
NetBeans Note: Folks that use NetBeans may not know that NetBeans does the right thing for JSP web-apps deployed to the SJSAS 8.1, 8.2, and GlassFish. Web-apps are directory deployed (by default) and JSP files are copied to the "deployment" directory when they are saved in the editor. So, you can edit and reload your JSP pages... no redeploy is required!