Shortening Java Programming Time with JavaRebel Lincoln NE

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

Mesa Corporation
(402) 489-9303
8231 Northwoods Drive
Lincoln, NE
Computers and Equipment Wholesale and Manufacturers, Computer Peripherals, Software Design and Development, Computer Software

Data Provided by:
(402) 437-9115
3120 Pine Lake Road
Lincoln, NE
M-F 8-9, Sa 9-7, Su 11-6*

Gc Image LLC
(402) 474-2942
201 N 8th St
Lincoln, NE
Materials Systems Software Inc
(402) 327-8456
245 S 84th St
Lincoln, NE
Centrix Solutions Inc
(402) 488-3990
4910 Normal Blvd
Lincoln, NE
(402) 467-1118
4940 O Street
Lincoln, NE
Recycling Services
Recycling Desk
$3 Ink & Toner Credit
Mon-Fri: 8:00am-9:00pm Sat: 9:00am-8:00pm Sun :10:00am-6:00pm

(402) 434-2828
5000 Central Park Dr
Lincoln, NE
Digitech Systems Inc
(402) 484-7777
111 Piazza Ter
Lincoln, NE
Mailing List Computer Services Inc
(402) 475-8844
140 N 8th St
Lincoln, NE
Salt Creek Software Inc
(402) 476-7115
2335 S 13th St
Lincoln, NE
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