Hot Deployment in JDeveloper 12c - Don't Stop/Start Your App
I still see developers stopping/starting their application on the embedded WebLogic server each time that they make a change or addition to their code..
Join the DZone community and get the full member experience.Join For Free
Old habits are hard to get rid off, and I still see long time users of JDeveloper (and also many new users) who are stopping/starting their application on the embedded WebLogic each time that they make a change or addition to their code.
Well you should stop it! (I mean stop stopping the application).
For a while now, JDeveloper has support for hot deployment that means that when you do most of the changes to your code you just need to do save-all followed by a rebuild of your viewController project - and that's it.
You can then go to your browser and reload your page - and the changes will be reflected there. This will not only save you the time it takes to undeploy and redeploy your app, it will also reduce the amount of memory you use since frequent redeployment of the app on the embedded WebLogic leads to bigger memory consumption.
In the demo below I use JDeveloper 12.1.3 to show you that I can just do the save->rebuild and pick up:
- Changes in the JSF file
- Changes to the JSF configuration file adfc-config.xml
- New classes that are added to both the model and viewController projects
- Changed to the ADF configuration files (pagedefs, data binding, data controls)
So for most cases, you should be covered with this hot-deployment capability.
There are some cases that will require a redeploy of the application (for example if you add a new skin css file, or if you change some runtime configuration of your app in web.xml) but for most cases you don't need to continue with the stop/start habit.
Published at DZone with permission of Shay Shmeltzer, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.