You are here

Using JRebel (Deprecated)

You can use JRebel alongside a Test Driven Development (TDD) approach. Please note that as of Alfresco SDK 2.0 this approach has been deprecated, but is included here as it may be useful to those who are currently working with JRebel.
One of the problems with developing Java applications for Alfresco is that very often it is necessary to restart the application server after making changes to Java source code. This slows down the development time considerably. One solution to this is to use a "hot deploy" technology such as JRebel.

JRebel allows you to change code and deploy it, without having to restart the application server (such as Tomcat).

This significantly reduces development time, as code changes can be "hot deployed", without the need to restart the application server. This complements a Test Driven Development approach, as changes can be made to code, tests run, and the changes verified, without the need for time-consuming restarts.
Important: JRebel-related functionality, while still available, has been deprecated and is no longer supported.

There are two versions of this tutorial, the first looks at using JRebel where you prefer a command line approach to building and running your project. The second looks at using JRebel with the Eclipse IDE. Note that you can actually use JRebel in both scenarios, so you can use the Alfresco SDK and JRebel both on the command line and in Eclipse with the same project.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.