Shortening Java Programming Time with JavaRebel Fayetteville NC
M-F 8-9, Sa 9-8, Su 12-6*
Pine Level, NC
Computers and Equipment Repair and Maintenance, Computer and Equipment Dealers, Computer Supplies Parts and Accessories, Computer Software, Computer Networks
Hardware Wholesale and Manufacturers, Bookstores, Computer and Equipment Dealers, Computer Software, Business Software
Computers and Equipment Repair and Maintenance, Web Site Hosting, Computer Software, Internet Service Providers, Web Site Design
Mon 10:00 AM-10:00 PM
Tue 10:00 AM-10:00 PM
Wed 10:00 AM-10:00 PM,
Internet Consultants, Computer Software, Computer Network Hardware, Communications Services
$3 Ink & Toner Credit
Mon-Fri: 7:00am-9:00pm Sat: 9:00am-9:00pm Sun :10:00am-6:00pm
Computers and Equipment Repair and Maintenance, Computer and Equipment Dealers, Computer Hardware and Supplies, Computer Software, Computer and Software Stores
MasterCard, Discover, VISA
Computers and Equipment Repair and Maintenance, Computer Supplies Parts and Accessories, Computer Software, Computer Networks
Personal Checks, Money Orders, Debit Cards, VISA, MasterCard
Computer and Equipment Dealers, Computer Software, Computer and Software Stores
Internet Services, Computer Hardware and Supplies, Computer Software, Internet Service Providers
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