The problem is, on some machines this hot-deployment procedure takes aThere is a verification task that must be run to ensure that the code is not evil. The result of this is cached so it is only the first time.
ridiculously long time. At present the application is less than 200
classes and the jar file is about 300K. On one machine it takes about a
minute and a half to do this for each task, whereas on another machine
it takes less than 10 seconds. And when you multiply that by 50 or 100
tasks, you can't even call it lukewarm deployment.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.