Skip to main content

JRebel version 3.5 released

I6 November released JRebel version 3.5. JRebel is an award winning productivity tool for Java EE development. JRebel maps your project workspace directly to your running application. When a developer makes a change to any class or resource in their IDE the change is immediately reflected in the application, skipping the build and redeploy phases. See the leaflet here
It takes only a few simple steps to configure and works out.
1) Download the installer from the following location
http://www.zeroturnaround.com/jrebel/current
2) Run the setup file
3) Add JRebel plugin in the projects root maven pom.xml as follows:
<plugin>
  <groupId>org.zeroturnaround</groupId>
  <artifactId>jrebel-maven-plugin</artifactId>
  <executions>
    <execution>
      <id>generate-rebel-xml</id>
      <phase>process-resources</phase>
      <goals>
        <goal>generate</goal>
      </goals>
    </execution>
  </executions>
</plugin>
This will generate JRebel configuration file rebel.xml automatically on every build. If you want to generate the rebel.xml manually run mvn jrebel:generate -Drebel.xml.dir=OUTPUT_DIRECTORY

4) Now you have to configure Weblogic application server as follows:
Go to $DOMAIN_HOME/bin and create the file startWeblogic-jrebel.sh with the following contents:
#!/bin/bash
export REBEL_HOME=/Applications/ZeroTurnaround/JRebel

export JAVA_OPTIONS="-noverify -javaagent:$REBEL_HOME/jrebel.jar $JAVA_OPTIONS"
./startWeblogic.sh $@
5) Start the server by the above script and you should see the following JRebel poster on console
6) Now you can deploy your application on weblogic server and JRebel will take care of it. After successful deployment JRebel will notice which module he will monitor with physical path. JRebel will indicate the directories it is monitoring for changes and will issue a "Reloaded class XXX" message every time you use a changed class.
 Also

Comments

Popular posts from this blog

Apache Ignite deep dive, SQL engine

Apache Ignite  is an open source memory-centric distributed database, caching and comput- ing platform. From the beginning, it was designed as an in-memory data grid for developing a high-performance software system. So, it’s core architecture design is slightly different from the traditional NoSQL databases, which can simplify building modern applications with a flexible data model and simpler high availability, high scalability.     Moreover, to understand how to design application with any databases or framework properly, you must understand the architecture of the database or framework itself. By getting a better idea of the system, you can solve different problems in your enterprise architecture landscape, can select a comprehensive database or framework that is appropriate for your application and get the maximum benefits from the system. In this article we are going to explore the Apache Ignite SQL engine.      Under the hood...

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title  The Apache Ignite book  has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...