Dear All, What I expect is that a jboss server is always running. Then run the cactus testing from Eclipse. Everytime a cactus is run, it compiles everything. If the new .ear is newer than the one already deployed in jboss, deploy it (replacing the old .ear in jboss). Then run the testcases.
The problems I am having are: 1. Startup the jboss (with no .ear deployed). Then run the ant task to do the cactus test in Eclipse. I've set the startUpWait to be 5000. Everything runs well, except that it shutdown jboss automatically after the test, which is not what I want. 2. Startup the jboss (with a .ear deployed). Then modify the testcases and rerun the cactus test in Eclipse. I noticed that the old .ear deployed in jboss was not replaced by the new .ear. And thus the testing result always remain the same, no matter how I change the testcases. I tried to search in cactus website and google. But I still have the following questions: 1. How exactly to control whether I use hot-deploy or not? 2. How exactly to control whether to shutdown the server after testing or not? 3. How exactly to decide at what cases the old .ear deployed in the server will be replaced by the newer generated .ear file? 4. Where could I find a full reference on the cactus related ANT tasks? I think http://jakarta.apache.org/cactus/integration/ant/task_cactus.html is not comprehensive. For example, "startUpWait" is not covered. Thanks, Stan __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
