RE: Log4J Issues
Hi Jason, -Original Message- From: Robertson, Jason [mailto:[EMAIL PROTECTED]] Sent: 02 May 2002 18:26 To: 'Cactus Users List' Subject: Log4J Issues I'm having a bear of a time getting my log4j setup working with the final 1.3 that was working fine with my dev build of a couple months ago. Some of it was me not updating my property files, but I have found a few issues: 1. On the server side, I need cactus.properties in the classpath. This is necessary so that LogService can find the 'cactus.enableLogging = true' property and enable the logging. The docs say this is only necessary on the client side. Not true. Check the doc. It says (referring to cactus.properties) : First and foremost, this file is completely optional on the server side (whereas it is mandatory on the client side). It is only used to turn on Cactus internal logging on the server side. 2. The docs also say that default log_client.properties and log_server.properties files are in cactus.jar, but they are not. That's right ... It was previously and for some reason I removed them (still don't know if I did this on purpose !). In the end it is better this way I think. But I'd like to know what others think. Should we put it back in the jar file ? Anyway, I've just modified the doc. 3. I'm getting duplicate entries for each log line. I doubt this is a Cactus problem, anyone else seeing this? A log4j-1.2rc1 issue? this, you solved yourself I believe. 4. I no longer see my EJB's log statements (I'm testing EJBs via ServletRedirector). I also don't see any errors (e.g., 'please initialize the log4j subsystem properly') - I just don't see anything. This worked fine before. Same. If anyone has ideas, please let me know! Jason -Vincent -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: testSendCookie error - TestSampleServlet
Hi Roger, -Original Message- From: yuguang sun [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 00:32 To: Cactus Users List Subject: RE: testSendCookie error - TestSampleServlet Hello Vincent, Thanks a lot for your message. I have found out the reason which caused the exception. In the beginSendCookie() method of sample servlet, the statement: theRequest.addCookie(testcookie, thisisacookie); is not fit to test servlet on remote machine. In WebRequest.java, the addCookie() method with two parameters means to set domain to localhost, but there is no web server running on my localhost. Ah yes, you're right. I am testing with my container running on the same machine. You have a good point. I shall mention this somewhere in the Samples Howto. Thanks. By the way, I think CACTUS is an excellent program. I wonder if there is a design document like class diagram etc. available for users to read. On the other side that in the future, we probably met similar problems. Things will be easier If we can print out messages to figure out if is caused by the wrong way to use CACTUS or some thing wrong with the program under test. Thanks for the compliment. Yes, there are design documents. Check http://jakarta.apache.org/cactus/how_it_works.html (there is a UML sequence diagram if you click on the link at the top of the page) + textual explanations. Is that what you meant ? Thanks -Vincent Roger - Original Message - From: Vincent Massol [EMAIL PROTECTED] Date: Wed, 22 May 2002 09:23:07 +0100 To: 'Cactus Users List' [EMAIL PROTECTED] Subject: RE: testSendCookie error - TestSampleServlet Hi Roger, I have never tried to run Cactus on IPlanet. Some have done that in the past and have reported on this newsgroup (check the archives). I can't recall any specific problem WRT cookies. If you could enable cactus logging and send the relevant portion of log, that would help. Looking at line 406, it seems the reason is because HttpClient fails to create a valid cookie. This is probably due because Cactus is passing to it either an invalid domain or an invalid cookie path. Now, as to why it might be doing this ... we need the logs. Thanks -Vincent -Original Message- From: yuguang sun [mailto:[EMAIL PROTECTED]] Sent: 22 May 2002 00:58 To: [EMAIL PROTECTED] Subject: testSendCookie error - TestSampleServlet Hi! I try to run TestSampleServlet. But I get following exceptions. Does any one have idea about that? I am using iplanet 6 web server on DS-10. cactus version is 1.3 as well. E.E Time: 1.647 There were 2 errors: 1) testSendCookie(org.apache.cactus.sample.TestSampleServlet) java.lang.NullPointerException at org.apache.cactus.client.HttpClientHelper.addCookies(HttpClientHelper.ja va ;org/apache/cactus/util/log/LogAspect.java(1k):406) at org.apache.cactus.client.HttpClientHelper.dispatch22_connect(HttpClientH el per.java;org/apache/cactus/util/log/LogAspect.java(1k):165) at org.apache.cactus.client.HttpClientHelper.around22_connect(HttpClientHel pe r.java;org/apache/cactus/util/log/LogAspect.java(1k):1221) at org.apache.cactus.client.HttpClientHelper.connect(HttpClientHelper.java; or g/apache/cactus/util/log/LogAspect.java(1k):125) at org.apache.cactus.client.AbstractHttpClient.callRunTest(AbstractHttpClie nt .java;org/apache/cactus/util/log/LogAspect.java(1k):188) at org.apache.cactus.client.AbstractHttpClient.dispatch1_doTest(AbstractHtt pC lient.java;org/apache/cactus/util/log/LogAspect.java(1k):120) at org.apache.cactus.client.AbstractHttpClient.around1_doTest(AbstractHttpC li ent.java;org/apache/cactus/util/log/LogAspect.java(1k):1221) at org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpClient.ja va ;org/apache/cactus/util/log/LogAspect.java(1k):115) at org.apache.cactus.AbstractTestCase.runGenericTest(AbstractTestCase.java: 45 7) at org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133) at org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:400) at org.apache.cactus.sample.TestSampleServlet.main(TestSampleServlet.java:9 6) 2) testSendMultipleCookies(org.apache.cactus.sample.TestSampleServlet) java.lang.NullPointerException at org.apache.cactus.client.HttpClientHelper.addCookies(HttpClientHelper.ja va ;org/apache/cactus/util/log/LogAspect.java(1k):406) at org.apache.cactus.client.HttpClientHelper.dispatch22_connect(HttpClientH el per.java;org/apache/cactus/util/log/LogAspect.java(1k):165) at org.apache.cactus.client.HttpClientHelper.around22_connect(HttpClientHel pe
RE: How to pass parameters to a Cactus Test Case
Hi Marc, Good question. Several solutions that comes to mind : 1/ In beginXXX() send the parameter using and WebRequest.addParameter() and get it on the server side by calling request.getParameter() (in your setUp() for example). Agreed this is not nice as it modified your test case 2/ In Cactus 1.4dev every property defined in Cactus.properties is exposed as a Java System property. Thus you can add your own properties there and get them in your code using System.getProperty(). You'll have to put it in both cactus.properties (client side and server side) though (you can copy the same file to both locations). Would that do for you ? -Vincent -Original Message- From: Brette, Marc [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 10:02 To: 'Cactus Users List' Subject: How to pass parameters to a Cactus Test Case Hi, I have a Cactus test that should be used against several configurations. To fix ideas, this test accesses a database and I would like to use this same test when my database is SQLServer or Oracle. In my application, the database to use is defined by a configuration file. An easy to use method would be to give the file name as a command line argument of the test runner, and call the same test with different parameter in my Makefile/Ant but : - this should be given both to the test runner and of the web server - I already pass an argument (my server root path) as a System property (using -DrootPath=...), and I expect other tests to need such runtime argument. - It would be simpler to have such parameter defined in the Makefile/Ant, rather than hard-coded in the test. Does anybody have a method to provide such runtime argument to a test ? (note that this is already a JUnit problem, but with Cactus, as we have several JVM, the problem is worse) Thanks, Marc -- To unsubscribe, e-mail: mailto:cactus-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:cactus-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: How to pass parameters to a Cactus Test Case
Well, it answer my question as it confirm there is no standard method to do what I want :-) I will keep in mind the 1st method however (I still have to figure out how to pass the argument for it to be available in beginXXX). The 2nd method implies that for each execution of my test, I would need a different cactus.properties, which is not easily manageable. Thanks ! -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 11:26 To: 'Cactus Users List' Subject: RE: How to pass parameters to a Cactus Test Case Hi Marc, Good question. Several solutions that comes to mind : 1/ In beginXXX() send the parameter using and WebRequest.addParameter() and get it on the server side by calling request.getParameter() (in your setUp() for example). Agreed this is not nice as it modified your test case 2/ In Cactus 1.4dev every property defined in Cactus.properties is exposed as a Java System property. Thus you can add your own properties there and get them in your code using System.getProperty(). You'll have to put it in both cactus.properties (client side and server side) though (you can copy the same file to both locations). Would that do for you ? -Vincent -Original Message- From: Brette, Marc [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 10:02 To: 'Cactus Users List' Subject: How to pass parameters to a Cactus Test Case Hi, I have a Cactus test that should be used against several configurations. To fix ideas, this test accesses a database and I would like to use this same test when my database is SQLServer or Oracle. In my application, the database to use is defined by a configuration file. An easy to use method would be to give the file name as a command line argument of the test runner, and call the same test with different parameter in my Makefile/Ant but : - this should be given both to the test runner and of the web server - I already pass an argument (my server root path) as a System property (using -DrootPath=...), and I expect other tests to need such runtime argument. - It would be simpler to have such parameter defined in the Makefile/Ant, rather than hard-coded in the test. Does anybody have a method to provide such runtime argument to a test ? (note that this is already a JUnit problem, but with Cactus, as we have several JVM, the problem is worse) Thanks, Marc -- To unsubscribe, e-mail: mailto:cactus-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:cactus-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
using cactus for load testing
I am trying to establish if cactus is the best tool for what I want to do. I have searched the documentation, Javadoc and mailing list archive, but found very few references to using cactus for load testing of J2EE components. By this I mean, is there any mechanism by which I can hit my class under test (deployed on an app server) with multiple threads (such as with JunitPerf) in a cactus test case? Thanks, Forrest Hodgkins btw - I am very impressed by the speed of response and professionalism displayed in the mailing list. Forrest Hodgkins Vajra Software, Inc. 617-877-1306 [EMAIL PROTECTED] http://www.vajrasoftware.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: using cactus for load testing
Hi Forrest, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 13:39 To: [EMAIL PROTECTED] Subject: using cactus for load testing I am trying to establish if cactus is the best tool for what I want to do. I have searched the documentation, Javadoc and mailing list archive, but found very few references to using cactus for load testing of J2EE components. By this I mean, is there any mechanism by which I can hit my class under test (deployed on an app server) with multiple threads (such as with JunitPerf) in a cactus test case? Unfortunately no. Cactus is only meant to be a unit test tool. It is not geared towards stress testing. For that you should rather use a black box stress testing tool like JMeter. Thanks, Forrest Hodgkins btw - I am very impressed by the speed of response and professionalism displayed in the mailing list. Hey thanks. We're not always as prompt as we'd like to be but we try hard ... :-) -Vincent Forrest Hodgkins Vajra Software, Inc. 617-877-1306 [EMAIL PROTECTED] http://www.vajrasoftware.com -- To unsubscribe, e-mail: mailto:cactus-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:cactus-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
org.apache.cactus.util.ChainedRuntimeException: Not a valid response
Hello NG. First at all: Yes, I know from the thread with the same topic from 29 Apr 2002 Ken Adjei and I have read the answer from Laurent Duperval. For anybody, who haven't read the tread, here is the answer from Laurent: --- In my case, this happened when the server wasn't being accessed witht he correct URL. I also see occur periodically for no apparent reason. In that case, I restart the ant build and the problem usually goes away. --- I work with an BEA WebLogic Appserver 6.1 and the Cactus 1.3 from the jakarta-cactus-13-1.3.zip. I want to test an EJB. Therefor I wrote my own ServletTestCase. I can't find any mistakes by setting up the URL but I always get the same exception: org.apache.cactus.util.ChainedRuntimeException: Not a valid response Here is my cactus.properties - file: # Configuration file for Cactus. # Each project using Cactus need to have such a file put in the client side # CLASSPATH (Meaning the directory containgin this file should be in the client # side CLASSPATH, not the file itself of course ... :) ) # Defines the URLs that will be used by Cactus to call it's redirectors. # You need to specify in these URLs the webapp context that you use for your # application. In the example below, the context is test. # Web app Context under which our application to test runs cactus.contextURL = http://localhost:7002/TestBenutzerZugriff # Default Servlet Redirector Name. Used by ServletTestCase test cases. cactus.servletRedirectorName = ServletRedirector # Default JSP Redirector Name. Used by JspTestCase test cases. #cactus.jspRedirectorName = JspRedirector # Default Filter Redirector Name. Used by FilterTestCase test cases. #cactus.filterRedirectorName = FilterRedirector # Enable Cactus internal logging #cactus.enableLogging = true Here is my web.xml ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN' 'http://java.sun.com/j2ee/dtds/web-app_2.2.dtd' web-app display-name/display-name description/description servlet servlet-nameServletRedirector/servlet-name servlet-classorg.apache.cactus.server.ServletTestRedirector/servlet-class /servlet servlet-mapping servlet-nameServletRedirector/servlet-name url-pattern/ServletRedirector//url-pattern /servlet-mapping ejb-ref ejb-ref-namede.jdi.ejb.ServiceLocatorHome/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homede.jdi.ejb.ServiceLocatorHome/home remotede.jdi.ejb.ServiceLocator/remote /ejb-ref /web-app Here is my weblogic.xml !DOCTYPE weblogic-web-app PUBLIC -//BEA Systems, Inc.//DTD Web Application 6.0//EN http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd; weblogic-web-app descriptionWebLogic Descriptor/description reference-descriptor ejb-reference-description ejb-ref-name de.jdi.ejb.ServiceLocatorHome /ejb-ref-name jndi-name de.jdi.ejb.ServiceLocatorHome /jndi-name /ejb-reference-description /reference-descriptor /weblogic-web-app Does anybody have an idea, why I get this error? Please help. JD __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Sie brauchen mehr Speicher für Ihre E-Mails? - http://premiummail.yahoo.de -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: org.apache.cactus.util.ChainedRuntimeException: Not a valid response
Hi Holger, I've just added a FAQ entry for this : http://jakarta.apache.org/cactus/faq.html#faq6 Please check it and tell me if it helped you solve the problem ! :-) Thanks -Vincent -Original Message- From: Holger Danske [mailto:[EMAIL PROTECTED]] Sent: 23 May 2002 15:04 To: [EMAIL PROTECTED] Subject: org.apache.cactus.util.ChainedRuntimeException: Not a valid response Hello NG. First at all: Yes, I know from the thread with the same topic from 29 Apr 2002 Ken Adjei and I have read the answer from Laurent Duperval. For anybody, who haven't read the tread, here is the answer from Laurent: --- In my case, this happened when the server wasn't being accessed witht he correct URL. I also see occur periodically for no apparent reason. In that case, I restart the ant build and the problem usually goes away. --- I work with an BEA WebLogic Appserver 6.1 and the Cactus 1.3 from the jakarta-cactus-13-1.3.zip. I want to test an EJB. Therefor I wrote my own ServletTestCase. I can't find any mistakes by setting up the URL but I always get the same exception: org.apache.cactus.util.ChainedRuntimeException: Not a valid response Here is my cactus.properties - file: # Configuration file for Cactus. # Each project using Cactus need to have such a file put in the client side # CLASSPATH (Meaning the directory containgin this file should be in the client # side CLASSPATH, not the file itself of course ... :) ) # Defines the URLs that will be used by Cactus to call it's redirectors. # You need to specify in these URLs the webapp context that you use for your # application. In the example below, the context is test. # Web app Context under which our application to test runs cactus.contextURL = http://localhost:7002/TestBenutzerZugriff # Default Servlet Redirector Name. Used by ServletTestCase test cases. cactus.servletRedirectorName = ServletRedirector # Default JSP Redirector Name. Used by JspTestCase test cases. #cactus.jspRedirectorName = JspRedirector # Default Filter Redirector Name. Used by FilterTestCase test cases. #cactus.filterRedirectorName = FilterRedirector # Enable Cactus internal logging #cactus.enableLogging = true Here is my web.xml ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN' 'http://java.sun.com/j2ee/dtds/web-app_2.2.dtd' web-app display-name/display-name description/description servlet servlet-nameServletRedirector/servlet-name servlet-classorg.apache.cactus.server.ServletTestRedirector/servlet- class /servlet servlet-mapping servlet-nameServletRedirector/servlet-name url-pattern/ServletRedirector//url-pattern /servlet-mapping ejb-ref ejb-ref-namede.jdi.ejb.ServiceLocatorHome/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homede.jdi.ejb.ServiceLocatorHome/home remotede.jdi.ejb.ServiceLocator/remote /ejb-ref /web-app Here is my weblogic.xml !DOCTYPE weblogic-web-app PUBLIC -//BEA Systems, Inc.//DTD Web Application 6.0//EN http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd; weblogic-web-app descriptionWebLogic Descriptor/description reference-descriptor ejb-reference-description ejb-ref-name de.jdi.ejb.ServiceLocatorHome /ejb-ref-name jndi-name de.jdi.ejb.ServiceLocatorHome /jndi-name /ejb-reference-description /reference-descriptor /weblogic-web-app Does anybody have an idea, why I get this error? Please help. JD __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Sie brauchen mehr Speicher für Ihre E-Mails? - http://premiummail.yahoo.de -- To unsubscribe, e-mail: mailto:cactus-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:cactus-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
NullPointerException on Windows when executin runservertask
HI, I'm a Linux user and I see this problem on one of my colleagues' machine, who is on Windows. Has anyone ever seen this? It appears even before the Starting Weblogic Server message. L cactustests: BUILD FAILED java.lang.NullPointerException at sun.net.www.http.ChunkedInputStream.readChunkSize(ChunkedInputStream. java:162) at sun.net.www.http.ChunkedInputStream.prefill(ChunkedInputStream.java:1 87) at sun.net.www.http.ChunkedInputStream.init(ChunkedInputStream.java:94 ) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:749) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:613) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon nection.java:506) at org.apache.cactus.ant.StartServerHelper.readFully(Unknown Source) at org.apache.cactus.ant.StopServerHelper.execute(Unknown Source) at org.apache.cactus.ant.RunServerTestsTask.callStop(Unknown Source) at org.apache.cactus.ant.RunServerTestsTask.execute(Unknown Source) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:104) at org.apache.tools.ant.Task.perform(Task.java:217) at org.apache.tools.ant.Target.execute(Target.java:184) at org.apache.tools.ant.Target.performTasks(Target.java:202) at org.apache.tools.ant.Project.executeTarget(Project.java:601) at org.apache.tools.ant.Project.executeTargets(Project.java:560) at org.apache.tools.ant.Main.runBuild(Main.java:454) at org.apache.tools.ant.Main.start(Main.java:153) at org.apache.tools.ant.Main.main(Main.java:176) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Stress Testing of a Servlet using Cactus !!!
Hello, I was ableto run the cactus sample tests after carefully correcting mistakes related to cactus.properties file. But I'm struck at one place. Can we use cactus for Stress Testing the Servlet. I've written cactus test case to test a servlet. But for that I needed to write this SetUp() method where I had to call servlet = new FrontServlet() ; config.setInitiParameter(configFile,D:\frontservlet.xml) ; servlet.init(config) It works fine. If I want to do a stress test on my FrontServlet, ( I started using JUnitPerf) it is calling these test methods in different threads, but, since init() of the servlet is being called all the time and it does not mean a good stress test. Can anybody throw some light on this and advise, how I can do a stress testing on servlets using any open source software? Thanks in advance. Ravi Kiran Choppalli. From: Vincent Massol [EMAIL PROTECTED] on 05/23/2002 09:42 AM CET To: Ravi K Choppalli/NonAEXP/TRS/AEXP@AMEX cc: Subject: RE: Help getting Apache Cactus Sample to RUN !!! Hi Ravi, You should send Cactus related emails only to the cactus user mailing list where you'll get help from everyone. Send an email there and I'll answer you ! :-) P.S.: I have also added this to the Cactus FAQ. -Original Message- From: Ravi K Choppalli [mailto:[EMAIL PROTECTED]] Sent: 02 May 2002 20:44 To: [EMAIL PROTECTED] Subject: Help getting Apache Cactus Sample to RUN !!! Hello Vincent, I've seen your name very actively associated with Cactus. Could you please guide me to overcome the following problem. I tried looking for some assistance all over the web, but could find a proper source. Thanks, - Ravi. -- Forwarded by Ravi K Choppalli/NonAEXP/TRS/AEXP on 05/02/2002 12:49 PM --- From: Ravi K Choppalli on 05/02/2002 12:17 PM To: [EMAIL PROTECTED] cc: Subject: Help getting Apache Cactus Sample to RUN !!! Hi, I'm trying to run the sample which came with apache cactus (Testing Framework to test Servlets/Jsp's/ etc) I'm running Websphere3.5 server on my windows 2000 machine and added the SampleServlet ServletRedirector to it. When I try to run the sample by saying : E:\JAKART~1.3\SAMPLE~1\src\sample\org\apache\cactus\samplejava org.apache.cactus.sample.TestSampleServlet I get the following errors : 13 Test cases are there in that and all fail. 13) testRequestDispatcherInclude(org.apache.cactus.sample.TestSampleServlet) or g.apache.cactus.util.ChainedRuntimeException: Not a valid response at org.apache.cactus.client.WebTestResultParser.readRootElement(WebTestResu lt Parser.java;org/apache/cactus/util/log/LogAspect.java(1k):134) at org.apache.cactus.client.WebTestResultParser.dispatch29_parse(WebTestRes ul tParser.java;org/apache/cactus/util/log/LogAspect.java(1k):101) at org.apache.cactus.client.WebTestResultParser.around29_parse(WebTestResul tP arser.java;org/apache/cactus/util/log/LogAspect.java(1k):1221) at org.apache.cactus.client.WebTestResultParser.parse(WebTestResultParser.j av a;org/apache/cactus/util/log/LogAspect.java(1k):96) at org.apache.cactus.client.AbstractHttpClient.callGetResult(AbstractHttpCl ie nt.java;org/apache/cactus/util/log/LogAspect.java(1k):231) at org.apache.cactus.client.AbstractHttpClient.dispatch1_doTest(AbstractHtt pC lient.java;org/apache/cactus/util/log/LogAspect.java(1k):123) at org.apache.cactus.client.AbstractHttpClient.around1_doTest(AbstractHttpC li ent.java;org/apache/cactus/util/log/LogAspect.java(1k):1221) at org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpClient.ja va ;org/apache/cactus/util/log/LogAspect.java(1k):115) at org.apache.cactus.AbstractTestCase.runGenericTest(AbstractTestCase.java: 45 7) at org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133) at org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:400) at org.apache.cactus.sample.TestSampleServlet.main(TestSampleServlet.java:9 4) FAILURES!!! Tests run: 13, Failures: 0, Errors: 13 (SAME Error for all 13) Contents of my cactus.properties file reads as follows : (It is in the classpath) # Configuration file for Cactus. # Each project using Cactus need to have such a file put in the client side # CLASSPATH (Meaning the directory containgin this file should be in the client # side CLASSPATH, not the file itself of course ... :) ) # Defines the URLs that will be used by Cactus to call it's redirectors. # You need to specify in these URLs the webapp context that you use for your # application. In the example below, the context is test. # Web app Context under which our application to test runs cactus.contextURL = http://localhost/inst/SampleServlet # Default Servlet Redirector Name. Used
