Shortening Java Programming Time with JavaRebel Chico CA

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

SunCloud Software SuperStore
(530) 532-1790
28 Sun Cloud Circle
Oroville, CA
Services
Computer and Equipment Dealers, Computer Hardware and Supplies, Computer Software, Computer and Software Stores, Computer Training

Data Provided by:
Computer Zone
(530) 224-7291
PO Box 1104
Chico, CA
 
Garden Walk Mall
(530) 345-2820
225 Main St
Chico, CA
 
Computer Learning Center
(530) 345-4444
2201 Pillsbury Rd Ste 108
Chico, CA
 
Gaynor Telesystems Inc
(530) 895-8442
669 Palmetto Ave Ste J
Chico, CA
 
Staples
(530) 533-1718
2150 Feather River Blvd
Oroville, CA
Recycling Services
Recycling Desk
$3 Ink & Toner Credit
Hours
Mon-Fri: 8:00am-8:00pm Sat: 9:00am-7:00pm Sun :10:00am-6:00pm

Help-U-Plan
(530) 894-2872
660 Manzanita Ct
Chico, CA
 
Favor Software
(530) 899-8878
30 Independence Cir
Chico, CA
 
Cybered Inc
(530) 899-1212
375 Airpark Blvd
Chico, CA
 
Effortless Information Systems
(530) 892-1798
1830 Mulberry St
Chico, CA
 
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