From: Clover, J. <Jam...@di...> - 2003-06-18 18:58:42
|
Shouldn't this type of testing (i.e., it requires the app server to be running for the test) be 5-10% of your overall testing? You may want to investigate things like Junit and debugging under JUnit for 90% of your testing needs - you can get much faster turn around time for the vast majority of your testing. Then you only need to do this slower testing for a very short amount of time. James ------------ James Clover Lead Engineer, Disney Enterprise Portal james -dot- clover -at- disney -dot- com -----Original Message----- From: Peng Zhao [mailto:pz...@cs...]=20 Sent: Tuesday, June 17, 2003 2:40 PM To: jbo...@li... Subject: [JBoss-user] Developing and debuging I met a big problem when developing and debuging. If I deploy the application as a "war" file, the jboss needs about 30 seconds to deploy it. Although it is not too long, for developing and debuging it is not affordable! The time for waiting is longer than the time for fixxing the bug! If I deploy the application as a directory (e.g. "app.war"), the .jsp can be reloaded when I replace a .jsp file in the directory. But the .class file can not be updated once it has run. It seems the jboss has a cache for the loaded .class file. Because the debuging<->deploying is so slow, I wasted a lot of time for even fixxing a small bug. Furthermore, the .jsp is so slow when first loaded from the web-client. Is that usual? Thanks! Peng ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ JBoss-user mailing list JBo...@li... https://lists.sourceforge.net/lists/listinfo/jboss-user |