I came across the term "exploded development" on this site...
http://www.zeroturnaround.com/javarebel/support-matrix/
and remembered hearing it before in relation to working with Java web applications. From what I can tell it is something to do with deploying your .war file as an extracted/raw set of files. Instead of using an ANT/Maven task to deploy a war file to the application server each time you want to try your code changes you are telling the application server to server the contents of a folder where the contents of the war are deployed "raw".
Am I on the right track? If anybody has a solid understanding of what this term means and the implications of using it that would be great.
An exploded deployment is an application which is not packaged in a . war, . ear or . jar file but it's contained in a directory using these extensions (. ear, .
An Exploding Code is a code that represents a group of service codes that are commonly used together. This feature is designed to save you time while entering services on the Walkout Statement or Treatment Plan.
Using exploded deployment allows updating application without redeploying or restarting the server. The server doesn't need to unpack the web application when it's deployed, it just uses the files that are present in the directory.
An application in exploded form has a full directory structure, with no JAR or other archive files. An application in archive form is a standard J2EE application EAR file that packages WAR and EJB JAR modules.
Yes exploded means than instead of deploying a WAR/EAR
file to your application server to test your application you point your application server at a folder containing the unzipped (exploded) contents of what would be inside the WAR/EAR file.
This makes development quicker as most application servers support Hot Deploy where you can change the code/JSPs etc and these changes will be reflected almost immediately in the running application.
The Tomcat plugin in Eclipse essentially uses this technique. The only thing to be careful of is that after many hot deploys most application servers start to run out of memory in the PermGen space and need restarting (well i've had this problem with Weblogic and Tomcat).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With