We know for a fact that JDeveloper is used for developing massive Java web applications where redeploys are a big pain. And we have also noticed that JDeveloper users are quite fond of running their application servers remotely: on a local virtual machine, on Docker, or on a true remote server. We have now filled this gap: as of JRebel 2018.2.5, our JDeveloper plugin supports working with remote servers. Take a look at this short overview!.
JRebel for JDeveloper is what you need if you’re running your application server anywhere other than your own local main OS. Scenarios include virtualizing your application server environment using Docker or Vagrant, running on a corporate central server, or using any of the PaaS offerings (Cloud Foundry, OpenShift) to host the server.
Under the hood, the remote server support syncs your changes to the remote server over HTTP/HTTPS. Otherwise, it’s the good old JRebel experience: your IDE compiles your Java changes, the JRebel IDE plugin sends them to the server, and the JRebel Agent reloads them, saving you the build and redeploy time. Don’t worry about slow network transfers either; JRebel syncs only the classes and resources that you changed. It will be blazing fast.
On the remote server side, you can be running any Java application server that is supported by JRebel – essentially all relevant servers in the ecosystem.
This feature enables you to configure a remote server URL for each of your Java projects. While configuring, use the “Test connection” button to make sure that JRebel IDE plugin can contact the JRebel Agent on your remote server. Each project you want to sync to a remote server should be set up separately.
Let us know what you think of this new feature. I am eagerly awaiting your feedback. Please send it to firstname.lastname@example.org.
To get started with the remote servers feature, check out these setup instructions in our manual. Install JRebel for JDeveloper 2018.2.5 or later and enjoy coding – without redeploys!