>One of the big advantages of a quasi-intrepretive language like Java is > precisely that the repetitive code/compile/test-run cycle is quick. > EJB changed all this. They stuck a rather long, tedious, and often >painful deployment phase right between compile and test-run, often breaking the > development cycle with 10 to 20 minute breaks.
We also had this problems until we switched to JBoss/Tomcat as "development-platform"*. Deployment is reduced to compiling, packaging (which is done automatically by the IDE) and copying. This job is done in about 1 minute (Our app consists of about 1000 class files). No further steps are required. Simply compile, copy, run. Believe me it's really FUN. Furthermore we can test our code locally. (Every client has it's own installation of JBoss/Tomcat. Local databases are supported on demand (Interbase)) Only once a day we deploy the tested code to our target platform (central EJB-Server and database) to perform final tests. This solves not the problem of debugging. But because we can test our projects locally we can catch errors using log-files easily. And this usually is done much faster than stepping through the code. But the discussion "Log-files vs. code-stepping" is another one... Regards, Andreas *In fact it's now one of our supported production environments for smaller projects. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
