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

Add a detector customised to FindBugs

The tools of static analysis of code allow to discern automatically some anomalies of an application. More anomalies are fast less discerned their cost of correction is high. Some people think that if the correction of a bug costs 1 during the stage of development, it will cost 10 in stage of recipe and 100 in production. The objectives of these tools are noble: discern a maximum of anomalies during the stage of development and reduce the number of bugs while returning more competitive and more homogeneous code. It is about one of the tools of which the developers have to guarantee the quality of their code. The most knowing and used in the world Popular dance are Checkstyle, PMD and FindBugs. allows, for example, to raise alerts in case of use of stocks _en dur_ in code while a constant would be the welcome. PMD discerns between others the presence of blocks wrestling spaces and FindBugs discerns the use of method equals on objects having no same David Hovemeyer type and William Pugh, the creators of FindBugs, decided not to control the problems of style or of format and limit themselves in search of true bugs.

The main danger of this type of tool is to drown the developer in a crowd of information not corresponding to its need. Rules being predefined in general by these tools, they all cannot apply to all contexts. To avoid this bad analysis and the lifting of false positive, it is possible in general to configurer tools to hurry up, to deactivate or to change these rules at request.

Moreover, so consequent is, the number of rules offered remains limited. It would be however practical to add to the need our own rules to be of benefit in the best of these tools. It is what one we are going to make following the ticket. As usual addition is relatively well researched for Checkstyle and PMD, we will be interested here in the creation of a new detector FindBugs.

Read the continuation of this article