Blog Xebia France

JavaRebel Recharge your classes without redeployer

Small express opinion poll: you have ever never determined an error just after a test of deployment making you redeploy your application faster than envisaged? How long does your application put to expand? Did you count how much times you redeployed her during your last developments?

No, we will introduce here no magical method preventing bugs, nor on the contrary any excuse to dash off your unit tests and your tests of integration. The purpose of this article is to introduce the mechanisms which we have to avoid the losses of time linked to the upturn of your applications. This ticket follows last XKE (Xebia Knowledge Exchange) of Thursday, November 6th during which I introduced JavaRebel.

This tool allows you to optimise your cycle of development by reducing at the very least the stages of redeployment of your applications via an advanced mechanism allowing the recharging heat of classes.

This ticket stands out in the following way:

• We will begin by describing the functioning of mode Debug Java with the presentation of JPDA
• We will itemise then the functioning of HotSwap, which allows us to change in heat the body of methods.
• We will approach then the mechanism of recharging of classes offered by JavaRebel.
• And finally, we will end by a quick return of experience on the product

Read the continuation of this article