Jrebel configuration eclipse9/21/2023 ![]() ![]() This tutorial assumes that you are using Eclipse 3.x (with Oracle Enterprise Pack for Eclipse installed) with WebLogic 9.x or later. Most of the steps will be applicable to other versions as well, but it may look different from the screenshots included. STEP 2: Installing JRebel Eclipse IDE plugin.STEP 3: Make a rebel.xml for your application.STEP 4: Configuring the Eclipse WTP IDE.Configuring the Eclipse WTP IDE workaround.STEP 2: Installing JRebel Eclipse IDE plugin The latest stable version of JRebel can be downloaded here. The JRebel Eclipse IDE plugin was introduced with JRebel 2.0 and makes configuring and using JRebel considerably easier. You can install the plugin by going to Help » Software updates » Available software » Add site and use the URL as the update site. STEP 3: Make a rebel.xml for your application #INSTALL JREBEL ECLIPSE PLUGIN INSTALL# In order to do it’s magic, JRebel needs to know where your classes and resources are. We’ll use a rebel.xml configuration file to tell it. This is mandatory when you deploy your app as a WAR/EAR. You’ll need to have one rebel.xml file per module. The rebel.xml configuration file should be placed in your WEB-INF/classes directory in the case of a web module and in the jar root in the case of an ejb module. Put it in the root of a source or resource folder in your project (the same place where the. If you use Maven you can use the JRebel Maven plugin that will generate the rebel.xml in accordance with the module pom.xml as described in the Maven Plugin configuration manual. ![]() In 99% of cases, people tend to use one module per project. If your project is one of the exceptions, edit the file manually as described in the Installation manual, otherwise generate the rebel.xml like this:Ĭlick on your project and pick Generate rebel.xml In these cases, the JRebel Eclipse IDE plugin can generate the rebel.xml file for you, on a per project basis. You may skip this step if you run Weblogic outside of the Eclipse IDE. Open the Servers View and double click the BEA WebLogic Server that your application is deployed to (if you don’t see the Servers View go to Window » Show View » Server s). Open Publishing and choose Never publish automatically. It may seem wrong to disable automatic publishing, but as JRebel will take care of updates from now on, it would just slow you down. Open JRebel Integration and check Enable JRebel agent. STEP 4a: Configuring the Eclipse WTP IDE workaround NB! With the current version of the Eclipse JRebel plugin checking the checkbox does NOT WORK. Until we update our JRebel Eclipse plugin you have to manually enable JRebel for the Weblogic Server. You would need to manually edit the startup script of the server. Set JAVA_OPTIONS=-noverify -javaagent:C:\javarebel.jar %JAVA_OPTIONS% You will need to copy the following line as the first line of the file Luckily it is quite easy and the startup script can be opened for editing from the server view from the last step.Ī text file will open. #INSTALL JREBEL ECLIPSE PLUGIN INSTALL#.Src/main/java/org/exoplatform/jrebel/portlet/MyPortlet.java package Once created, you can add the source file for the portlet: Check Create a simple project (skip archetype selection).New Portlet Projectīefore going further with JRebel, you need to create a new portlet project: Simply follow the first 3 steps in this tutorial on the JRebel website. The first step is to install JRebel in Eclipse. To learn how to start eXo Platform in Eclipse, check out this tutorial. JRebel integrates well with Eclipse, which we used in the following example. In this tutorial, we will demonstrate how to use JRebel to speed up development with eXo Platform. JRebel is a tool that enables developers to instantly reload changes in Java sources files, without having to redeploy the application or restart the server. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |