Shortening Java Programming Time with JavaRebel Syracuse NY

For programmers only: Change your Java code and keep on running without redeployment. Read on and know more.

Eastern Computer Warehouse
(315) 449-0111
5802 Bridge Street
East Syracuse, NY
Staples
315-455-2820
300 Northern Lights Plaza
Syracuse, NY
Staples
315-463-8040
3 Chevy Dr.
E. Syracuse, NY
Staples
315-488-4071
3736 Milton Ave.
Camillus, NY
Intercon Associates Inc
(585) 244-1250
95 Allens Creek Road # 200
Rochester, NY
Gamestop
(315) 622-0492
4155 State Route 31
Clay, NY
OfficeMax
315-449-4610
3471 Erie Blvd. East
Dewitt, NY
Staples
315-715-0112
4118 Rt. 31
Clay, NY
OfficeMax
315-458-0638
5671 East Circle Drive
Cicero, NY
TechNetPro Systems Inc.
(718) 972-8940
755 44th Street
Brooklyn, NY
Data Provided by:
 

Shortening Java Programming Time with JavaRebel

Edit-compile-test-edit-compile-test. This is the "software development cycle" all programmers know well, from "Hello World" onwards. JavaRebel ($59 for a one-year personal license, $129 for a one-year corporate single-user license) is a JAR file which will allow you to skip directly from "edit" to "test" while eliminating "compile" at least most of the time.

Using JavaRebel is extremely simple: Just pass an appropriate command when you invoke your Java Virtual Machine. It took me about 30 seconds to get it working in Eclipse. Once it's there, it's transparent--and useful. To test it, I launched an application, then, while the application was running, added in some additional output code to the event handler for a button. After a second or two, I received a notice in my console window that the relevant classes had been reloaded, and the button now executed its modified behavior. I can foresee this saving me a tremendous amount of debugging time. Even a few minutes a day saved re-launching apps adds up, over a year, to hours or even days of productivity, depending on re-deployment time after minor edits.

There are a few changes it can't handle--you can't change class hierarchy or implement new interfaces, for example, but it's unlikely you'd be making changes like that during a standard edit-compile-test cycle. There is also a risk factor; if the app you're working on is "live," and you are careless with your configuration, you could introduce new bugs into running code. However, that's a user error and hardly the fault of the program.

The trial version lasts for 30 days and prints a message in the console window when run. This should be long enough to determine if the utility provided is worth it.

Click here to read article at PC World