Re: Running Cactus tests in Eclipse
The cactus.properties file must be in the classpath. So you may change the file location and/or the build path in Eclipse so that it works. Hope it helps, Romain David Turley a écrit : At one point I was able to run my Cactus tests in Eclipse by starting up tomcat and running the tests as JUnit tests. Since then I changed my directory structure a bit to make things more sensible and convenient for the Ant integration, and now when I try to run an individual test in Eclipse, it complains about the cactus.contextURL. I have a cactus.properties file in my project's base directory, but something (the error and the fact that it doesn't work...;-) tells me that's not the right place... Where should I put it? What should I do with it? Is there another way to quickly run a test? It takes too long to build and cactify a war to make it convenient. Also, is anyone working on the Eclipse integration? I saw someone ask about downloading it a month ago or so, but there was never any response to his email. Thanks, David Turley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Cactus tests in Eclipse
Hi Lawrence, Thanks for the info. I'll keep my eye on WTP and watch for Cactus integration. --David Lawrence Mandel wrote: Hi David, Wanted to let you know the Eclipse Web Tools Platform (WTP) project [1] has started working on Eclipse integration for Cactus. I've recently had some mailing list discussions (on cactus-dev) with the Cactus team (well, really with Vincent) about how Cactus and WTP can collaborate on this. The short story is there isn't currently much in the way of Cactus tooling in WTP but WTP should be able to pick up the slack on Cactus integration in Eclipse in the coming WTP releases. [1] http://www.eclipse.org/webtools Lawrence Mandel Software Developer IBM Rational Software Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920 [EMAIL PROTECTED] David Turley [EMAIL PROTECTED] 08/26/2005 04:51 PM Please respond to Cactus Users List To Cactus Users List cactus-user@jakarta.apache.org cc Subject Running Cactus tests in Eclipse At one point I was able to run my Cactus tests in Eclipse by starting up tomcat and running the tests as JUnit tests. Since then I changed my directory structure a bit to make things more sensible and convenient for the Ant integration, and now when I try to run an individual test in Eclipse, it complains about the cactus.contextURL. I have a cactus.properties file in my project's base directory, but something (the error and the fact that it doesn't work...;-) tells me that's not the right place... Where should I put it? What should I do with it? Is there another way to quickly run a test? It takes too long to build and cactify a war to make it convenient. Also, is anyone working on the Eclipse integration? I saw someone ask about downloading it a month ago or so, but there was never any response to his email. Thanks, David Turley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Cactus tests in Eclipse
Okay, that makes sense. Thanks. Unfortunately that's not my only problem. For some reason I'm getting the following stack trace when I try to run my test cases: java.net.MalformedURLException: no protocol: /app/ServletRedirector at java.net.URL.init(URL.java:537) at java.net.URL.init(URL.java:434) at java.net.URL.init(URL.java:383) at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody0(HttpClientConnectionHelper.java:78) at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect_aroundBody1$advice(HttpClientConnectionHelper.java:306) at org.apache.cactus.internal.client.connector.http.HttpClientConnectionHelper.connect(HttpClientConnectionHelper.java) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.callRunTest(DefaultHttpClient.java:162) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody0(DefaultHttpClient.java:80) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest_aroundBody1$advice(DefaultHttpClient.java:306) at org.apache.cactus.internal.client.connector.http.DefaultHttpClient.doTest(DefaultHttpClient.java) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runWebTest(HttpProtocolHandler.java:159) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody0(HttpProtocolHandler.java:80) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest_aroundBody1$advice(HttpProtocolHandler.java:306) at org.apache.cactus.internal.client.connector.http.HttpProtocolHandler.runTest(HttpProtocolHandler.java) at org.apache.cactus.internal.client.ClientTestCaseCaller.runTest(ClientTestCaseCaller.java:144) at org.apache.cactus.internal.AbstractCactusTestCase.runBareClient(AbstractCactusTestCase.java:215) at org.apache.cactus.internal.AbstractCactusTestCase.runBare(AbstractCactusTestCase.java:133) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I have put all the servlet mapping stuff in my web.xml, but the error is the same with it in as it is without it. Anyone have any ideas why this is happening? It's probably something totally stupid I'm forgetting to do, but I can't figure it out :-P. Thanks, David Romain Thouvenin wrote: The cactus.properties file must be in the classpath. So you may change the file location and/or the build path in Eclipse so that it works. Hope it helps, Romain David Turley a écrit : At one point I was able to run my Cactus tests in Eclipse by starting up tomcat and running the tests as JUnit tests. Since then I changed my directory structure a bit to make things more sensible and convenient for the Ant integration, and now when I try to run an individual test in Eclipse, it complains about the cactus.contextURL. I have a cactus.properties file in my project's base directory, but something (the error and the fact that it doesn't work...;-) tells me that's not the right place... Where should I put it? What should I do with it? Is there another way to quickly run a test? It takes too long to build and cactify a war to make it convenient. Also, is anyone working on the Eclipse integration? I saw someone ask about downloading it a month ago or so, but there was never any response to his email. Thanks, David Turley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running Cactus tests in Eclipse
-Original Message- From: David Turley [mailto:[EMAIL PROTECTED] Sent: lundi 29 août 2005 20:17 To: Cactus Users List Subject: Re: Running Cactus tests in Eclipse Please disregard that last email... It WAS something stupid. So stupid it would be too embarrassing to relate the problem. I realized the problem almost immediately after sending the message, but it was too late to call it back... Give me the prize for stupidity today :-). Don't worry! We're so happy when the problem is not a Cactus issue that we forgive you right away ;-) [snip - Deleted to prevent further embarrassment :-)] -Vincent ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running Cactus tests in Eclipse
Does anybody know how to make Cactus work with Jrun 3.0?? Thanks Anjali -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, August 29, 2005 1:43 PM To: 'Cactus Users List' Subject: RE: Running Cactus tests in Eclipse -Original Message- From: David Turley [mailto:[EMAIL PROTECTED] Sent: lundi 29 août 2005 20:17 To: Cactus Users List Subject: Re: Running Cactus tests in Eclipse Please disregard that last email... It WAS something stupid. So stupid it would be too embarrassing to relate the problem. I realized the problem almost immediately after sending the message, but it was too late to call it back... Give me the prize for stupidity today :-). Don't worry! We're so happy when the problem is not a Cactus issue that we forgive you right away ;-) [snip - Deleted to prevent further embarrassment :-)] -Vincent ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running Cactus tests in Eclipse
Hi David, Wanted to let you know the Eclipse Web Tools Platform (WTP) project [1] has started working on Eclipse integration for Cactus. I've recently had some mailing list discussions (on cactus-dev) with the Cactus team (well, really with Vincent) about how Cactus and WTP can collaborate on this. The short story is there isn't currently much in the way of Cactus tooling in WTP but WTP should be able to pick up the slack on Cactus integration in Eclipse in the coming WTP releases. [1] http://www.eclipse.org/webtools Lawrence Mandel Software Developer IBM Rational Software Phone: 905 - 413 - 3814 Fax: 905 - 413 - 4920 [EMAIL PROTECTED] David Turley [EMAIL PROTECTED] 08/26/2005 04:51 PM Please respond to Cactus Users List To Cactus Users List cactus-user@jakarta.apache.org cc Subject Running Cactus tests in Eclipse At one point I was able to run my Cactus tests in Eclipse by starting up tomcat and running the tests as JUnit tests. Since then I changed my directory structure a bit to make things more sensible and convenient for the Ant integration, and now when I try to run an individual test in Eclipse, it complains about the cactus.contextURL. I have a cactus.properties file in my project's base directory, but something (the error and the fact that it doesn't work...;-) tells me that's not the right place... Where should I put it? What should I do with it? Is there another way to quickly run a test? It takes too long to build and cactify a war to make it convenient. Also, is anyone working on the Eclipse integration? I saw someone ask about downloading it a month ago or so, but there was never any response to his email. Thanks, David Turley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running Cactus tests in Eclipse
At one point I was able to run my Cactus tests in Eclipse by starting up tomcat and running the tests as JUnit tests. Since then I changed my directory structure a bit to make things more sensible and convenient for the Ant integration, and now when I try to run an individual test in Eclipse, it complains about the cactus.contextURL. I have a cactus.properties file in my project's base directory, but something (the error and the fact that it doesn't work...;-) tells me that's not the right place... Where should I put it? What should I do with it? Is there another way to quickly run a test? It takes too long to build and cactify a war to make it convenient. Also, is anyone working on the Eclipse integration? I saw someone ask about downloading it a month ago or so, but there was never any response to his email. Thanks, David Turley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
