Interesting! What you should get is pasted below.
Now, what I think might be getting you is excess settings. You know how you
can have a properties file in your user home directory that is included by
everything? I think that might be causing the maven war to fail.
Do me a favor and run maven war. That should produce a file in your samples
/target/maven-cactus-sample.war. Let me know if that happens. If so, then
I will nuke my maven, and rebuild from CVS and see what happens.
Eric Pugh
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample>maven
war
cactus:test
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
war:init:
java:prepare-filesystem:
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\classes
java:compile:
[javac] Compiling 5 source files to
C:\java\maven\plugins\maven-cactus-plugi
n-1.2\plugin-resources\sample\target\classes
java:prepare-filesystem:
java:compile:
java:jar-resources:
test:prepare-filesystem:
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\test-classes
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\test-reports
test:test-resources:
test:compile:
[javac] Compiling 1 source file to
C:\java\maven\plugins\maven-cactus-plugin
-1.2\plugin-resources\sample\target\test-classes
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.maven.cactus.sample.DummyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.361 sec
war:war:
[echo] Building WAR maven-cactus-sample
[war] Building war:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-res
ources\sample\target\maven-cactus-sample.war
war:
cactus:test:
[echo] Attempting to run tomcat4x target: cactus:test-tomcat-4x
cactus:test-tomcat-4x:
[echo] maven.cactus.tomcat4x.home = C:/java/tomcat
cactus:setup-tomcat-4x:
cactus:tomcat-4x-run:
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\cactus\tomcat4x\conf
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\cactus\tomcat4x\webapps
[copy] Copying 2 files to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plug
in-resources\sample\target\cactus\tomcat4x\conf
cactus:webapp:
war:init:
java:prepare-filesystem:
java:compile:
java:prepare-filesystem:
java:compile:
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.maven.cactus.sample.DummyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.02 sec
[unwar] Expanding:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-reso
urces\sample\target\maven-cactus-sample.war into
C:\java\maven\plugins\maven-cac
tus-plugin-1.2\plugin-resources\sample\target\cactus\maven-cactus-sample
java:prepare-filesystem:
java:compile:
cactus:compile:
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\cactus\classes
[javac] Compiling 3 source files to
C:\java\maven\plugins\maven-cactus-plugi
n-1.2\plugin-resources\sample\target\cactus\classes
cactus:webapp-update:
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample
cactus:merge-webxml:
[echo] You should provide in your project.properties a
maven.cactus.webxml w
eb.xml file to use. Using default web.xml
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\lib
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\lib
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\lib
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\lib
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\lib
[copy] Copying 4 files to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plug
in-resources\sample\target\cactus\maven-cactus-sample\WEB-INF\classes
cactus:deploy-tomcat-4x:
[copy] Copying 17 files to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plu
gin-resources\sample\target\cactus\tomcat4x\webapps\test
cactus:start-tomcat-4x:
[java] HttpConnector Opening server socket on all host IP addresses
[java] Starting service Tomcat-Standalone
[java] Apache Tomcat/4.1.18
[java] WebappLoader[/test]: Deploying class repositories to work
directory C
:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\
cact
us\tomcat4x\work\Standalone\localhost\test
[java] WebappLoader[/test]: Deploy class files /WEB-INF/classes to
C:\java\m
aven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\cactus\t
omca
t4x\webapps\test\WEB-INF\classes
[java] WebappLoader[/test]: Deploy JAR /WEB-INF/lib/aspectjrt-1.0.6.jar
to C
:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\
cact
us\tomcat4x\webapps\test\WEB-INF\lib\aspectjrt-1.0.6.jar
[java] WebappLoader[/test]: Deploy JAR /WEB-INF/lib/cactus-13-1.4.1.jar
to C
:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\
cact
us\tomcat4x\webapps\test\WEB-INF\lib\cactus-13-1.4.1.jar
[java] WebappLoader[/test]: Deploy JAR
/WEB-INF/lib/commons-logging-1.0.1.ja
r to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\targe
t\cactus\tomcat4x\webapps\test\WEB-INF\lib\commons-logging-1.0.1.jar
[java] WebappLoader[/test]: Deploy JAR /WEB-INF/lib/httpunit-1.5.jar to
C:\j
ava\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\cac
tus\
tomcat4x\webapps\test\WEB-INF\lib\httpunit-1.5.jar
[java] WebappLoader[/test]: Deploy JAR /WEB-INF/lib/junit-3.8.1.jar to
C:\ja
va\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample\target\cact
us\t
omcat4x\webapps\test\WEB-INF\lib\junit-3.8.1.jar
[java] WebappLoader[/test]: Reloading checks are enabled for this
Context
[java] ContextConfig[/test]: Missing default web.xml, using application
web.
xml only
[java] ContextConfig[/test]: Configured an authenticator for method
BASIC
[java] StandardManager[/test]: Seeding random number generator class
java.se
curity.SecureRandom
[java] StandardManager[/test]: Seeding of random number generator has
been c
ompleted
[java] HttpConnector[8080] Starting background thread
cactus:test-init:
cactus:init:
cactus:test-text:
[mkdir] Created dir:
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-re
sources\sample\target\cactus\resources
[copy] Copying 1 file to
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugi
n-resources\sample\target\cactus\resources
[junit] Running org.apache.maven.cactus.sample.TestSampleBodyTag
[junit] StandardWrapper[/test:JspRedirector]: Marking servlet
JspRedirector
as unavailable
[junit] StandardWrapperValve[JspRedirector]: Allocate exception for
servlet
JspRedirector
[junit] javax.servlet.ServletException: No servlet class has been
specified
for servlet JspRedirector
[junit] javax.servlet.ServletException: No servlet class has been
specified
for servlet JspRedirector
[junit] at
org.apache.catalina.core.StandardWrapper.loadServlet(Standard
Wrapper.java:859)
[junit] at
org.apache.catalina.core.StandardWrapper.allocate(StandardWra
pper.java:666)
[junit] at
org.apache.catalina.core.StandardWrapperValve.invoke(Standard
WrapperValve.java:214)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:643)
[junit] at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
line.java:480)
[junit] at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.j
ava:995)
[junit] at
org.apache.catalina.core.StandardContextValve.invoke(Standard
ContextValve.java:191)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:643)
[junit] at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Au
thenticatorBase.java:493)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:641)
[junit] at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
line.java:480)
[junit] at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.j
ava:995)
[junit] at
org.apache.catalina.core.StandardContext.invoke(StandardConte
xt.java:2415)
[junit] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHos
tValve.java:180)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:643)
[junit] at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorD
ispatcherValve.java:170)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:641)
[junit] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor
tValve.java:172)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:641)
[junit] at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
line.java:480)
[junit] at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.j
ava:995)
[junit] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardE
ngineValve.java:174)
[junit] at
org.apache.catalina.core.StandardPipeline$StandardPipelineVal
veContext.invokeNext(StandardPipeline.java:643)
[junit] at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipe
line.java:480)
[junit] at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.j
ava:995)
[junit] at
org.apache.catalina.connector.http.HttpProcessor.process(Http
Processor.java:1040)
[junit] at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProc
essor.java:1151)
[junit] at java.lang.Thread.run(Thread.java:484)
[junit] StandardWrapperValve[JspRedirector]: Servlet JspRedirector is
curren
tly unavailable
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.754 sec
[junit] [ERROR] TEST org.apache.maven.cactus.sample.TestSampleBodyTag
FAILED
[junit] Running org.apache.maven.cactus.sample.TestSampleFilter
[junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 1.532 sec
[junit] [ERROR] TEST org.apache.maven.cactus.sample.TestSampleFilter
FAILED
[junit] Running org.apache.maven.cactus.sample.TestSampleServlet
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.783 sec
BUILD FAILED
file:/C:/java/maven/plugins/maven-cactus-plugin-1.2/plugin-resources/scripts
/tom
cat.4x.jelly:26:50: <attainGoal>
file:/C:/java/maven/plugins/maven-cactus-plugin
-1.2/plugin-resources/scripts/tomcat.4x.jelly:68:64: <attainGoal>
null:292:52: <
fail> There were test failures.
Total time: 47 seconds
C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample>
-----Original Message-----
From: Akmal Sarhan [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 8:57 AM
To: Turbine Users List
Subject: Re: Testing with maven/cactus
here is what I get:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\3rdparty\maven-1.0-beta-9\plugins\maven-cactus-plugin-1.2\plugin-resource
s\sample>maven war cactus:test
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-9-SNAPSHOT
war:init:
java:prepare-filesystem:
java:compile:
java:prepare-filesystem:
java:compile:
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.maven.cactus.sample.DummyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,04 sec
war:war:
[echo] Building WAR maven-cactus-sample-1.0-SNAPSHOT
war:
cactus:test:
[echo] Attempting to run tomcat4x target: cactus:test-tomcat-4x
cactus:test-tomcat-4x:
[echo] maven.cactus.tomcat4x.home = D:/Programme/ApacheGroup/Tomcat 4.1
cactus:tomcat-4x-run:
cactus:webapp:
war:init:
java:prepare-filesystem:
java:compile:
java:prepare-filesystem:
java:compile:
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.maven.cactus.sample.DummyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,01 sec
[echo]
Either a war or a webapp must exist. Please call the War
plugin
first.
BUILD FAILED
file:/E:/3rdparty/maven-1.0-beta-9/plugins/maven-cactus-plugin-1.2/plugin-re
sources/scripts/tomcat.4x.jelly:26:50: <atta
inGoal>
file:/E:/3rdparty/maven-1.0-beta-9/plugins/maven-cactus-plugin-1.2/plugin-re
sources/scripts/tomcat.4x.jelly:60:5
5: <attainGoal>
file:/E:/3rdparty/maven-1.0-beta-9/plugins/maven-cactus-plugin-1.2/plugin-re
sources/scripts/tomcat.4x.je
lly:105:67: <copy>
E:\3rdparty\maven-1.0-beta-9\plugins\maven-cactus-plugin-1.2\plugin-resource
s\sample\target\cactus\ma
ven-cactus-sample not found.
Total time: 6 seconds
E:\3rdparty\maven-1.0-beta-9\plugins\maven-cactus-plugin-1.2\plugin-resource
s\sample>
regards
Akmal
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 13, 2003 2:23 PM
Subject: RE: Testing with maven/cactus
> okay,
> well, you got an error message about either a war or webapp must exist.
> However, you did call the war task! do me a favor, and try the sample
> app... just as a quick check of your install. this is where mine is:
> C:\java\maven\plugins\maven-cactus-plugin-1.2\plugin-resources\sample>
>
> When I run maven war cactus:test, it works. So please compare the
sample's
> properties to your properties.
>
> I put all my cactus testing properties locally in my project.properties,
and
> don't use a build.properties.
>
> Also, maven.cactus.container is no longer required. Just pointing to your
> tomcat home does the same thing.
>
> At any rate, verifying that your plugin version works with the sample will
> give us a baseline to start with. Then we can start tweaking Turbine
> related settings to get it to work with turbine.
>
> Eric
>
> -----Original Message-----
> From: Akmal Sarhan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 13, 2003 4:10 AM
> To: Turbine Users List
> Subject: Re: Testing with maven/cactus
>
>
> the build. properties did not seem to get through here it is again:
>
# --------------------------------------------------------------------------
> ---
> # build.properties.sample
> #
> # This is an example "build.properties" file, used to customize building
the
> # Cactus Servlet Sample for your local environment. Make any changes you
> need,
> # and rename this file to "build.properties" in the same directory that
> # contains the "build.xml" file.
> #
> # $Id: build.properties,v 1.1 2003/02/03 08:37:38 vmassol Exp $
>
# --------------------------------------------------------------------------
> ---
>
> # WARNING: The relative paths below are relative to the directory where
the
> # build.xml file is located.
>
>
# --------------------------------------------------------------------------
> ---
> # Mandatory properties
>
# --------------------------------------------------------------------------
> ---
>
> # The location of the Servlet API 2.3 jar
> servlet.jar = lib/servlet.jar
>
> # The location of the JSTL jar
> jstl.jar = lib/jstl.jar
>
> # The location of the JSTL jar
> standard.jar = lib/standard.jar
>
>
# --------------------------------------------------------------------------
> ---
> # Optional properties
>
# --------------------------------------------------------------------------
> ---
>
> # The port to use for starting the servers during unit testing. If not
> # sepcified, it defaults to port 8080.
> cactus.port = 8081
>
> # Servlet engine locations for the tests
>
> # Note: If you don't want to run the test on a given servlet engine, just
> # comment it's home property. For example, if you don't want to run
> the
> # tests on the Resin 2.x, comment the "cactus.home.resin2x"
property.
>
> #cactus.home.resin2x = c:/Apps/resin-2.1.6
> cactus.home.tomcat4x = D:/Programme/ApacheGroup/Tomcat 4.1
>
> maven.cactus.tomcat4x.home = D:/Programme/ApacheGroup/Tomcat 4.1
> maven.cactus.container = tomcat-4x
> maven.src.dir = WEB-INF/src/java
>
>
#maven.war.webxml=E:/3rdparty/tdk-2.2-rc2/webapps/taskwatcher_turbine/WEB-IN
> F/web.xml
> maven.war.webxml=${maven.src.dir}/../../web.xml
>
> ----- Original Message -----
> From: "Akmal Sarhan" <[EMAIL PROTECTED]>
> To: "Turbine Users List" <[EMAIL PROTECTED]>
> Sent: Thursday, March 13, 2003 10:08 AM
> Subject: Re: Testing with maven/cactus
>
>
> > Thank you Eric,
> >
> > I have tried the latest CVS head and have attached the exceptions that I
> > get, together with my build.properties file
> > thank you in advance and hope to be able to use the plugin pretty soon,
as
> > it will make life much easier ;-)
> >
> > regards
> > Akmal
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, March 12, 2003 5:34 PM
> > Subject: RE: Testing with maven/cactus
> >
> >
> > > ARgh!
> > >
> > > It turned out that the version of the maven cactus plugin was a local
> > copy.
> > > As I just recieved committer status, I applied my various patches that
> > made
> > > the plugin work. I can just imagine how frustrating it was to use the
> old
> > > broken one.
> > >
> > > If you feel like testing the new version, download maven cvs head.
> Build
> > > it. In the cactus/plugin-resources/sample is a sample project. Run
> that
> > > and verify the SampleServlet test works. Then you should be good.
> > >
> > > The sampleFilter and sampleTag are not working, some sort of web.xml
> issue
> > > that I don't understand.
> > >
> > > Good luck,
> > > Eric Pugh
> > >
> > > -----Original Message-----
> > > From: Akmal Sarhan [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, March 12, 2003 2:30 AM
> > > To: Turbine Users List
> > > Subject: Re: Testing with maven/cactus
> > >
> > >
> > > Thank you Eric,
> > >
> > > The reason why I wanted to use maven, is that I did not want to write
a
> > > property here and a property there, change this file and copy that
> file..
> > > you know
> > > but as you pointed out the maven plugin does not seem to be "finished"
> so
> > > I'd rather stick to my old cactus skeleton for the moment and hope
that
> I
> > > can use the plugin and perhaps, the eclipse one as well, at some
point.
> > >
> > >
> > > regards
> > > Akmal
> > >
> > > PS. my code is nearly identical to yours, thank you!
> > >
> > >
> > > ----- Original Message -----
> > > From: <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Tuesday, March 11, 2003 1:08 PM
> > > Subject: RE: Testing with maven/cactus
> > >
> > >
> > > > okay, well, here is the current situation with the cvs head maven
> cactus
> > > > plugin. This is a little OT for the turbine list, but may help
> others!
> > > > Right now, if you do not start up Turbine yourself in your setUp
> method,
> > > but
> > > > instead rely on the web.xml to startup turbine, then nothing
happens.
> > The
> > > > reason is that the maven cactus plugin doesn't merge your web.xml
with
> > the
> > > > default web.xml. That means that turbine never gets started.
> > > Temporariily,
> > > > there is a web.cactus.xml file that you can customize and will be
used
> > > > instead of your web.xml. Alternatively, you can just start up
> Turbine.
> > > > Take a look at this (also there is something on the wiki):
> > > >
> > > >
> > > > protected RunData data = null;
> > > > protected Context context = null;
> > > > private Turbine turbine = null;
> > > >
> > > > public void setUp() throws Exception {
> > > > super.setUp();
> > > > config.setInitParameter("properties", "/WEB-INF/conf/" +
> > > > getTurbinePropertiesFileName());
> > > > turbine = new Turbine();
> > > >
> > > > turbine.init(config);
> > > >
> > > > data = RunDataFactory.getRunData(request, response, config);
> > > > context = TurbineVelocity.getContext(data);
> > > > System.out.println("Setup: Resetting Data");
> > > >
> > > > // initialize your database connection here
> > > > IDatabaseConnection connection = new
> > > > DatabaseConnection(Torque.getConnection("default"));
> > > >
> > > > // initialize your dataset here
> > > > IDataSet dataSet = null;
> > > > String xmlFile =
> > > >
> > >
> >
>
TurbineServlet.getServletContext().getRealPath("WEB-INF/data/export_simple_w
> > > > orkorders.xml");
> > > > dataSet = new FlatXmlDataSet(new FileInputStream(xmlFile));
> > > >
> > > > try {
> > > >
> > > > InsertIdentityOperation.CLEAN_INSERT.execute(connection, dataSet);
> > > > }
> > > > finally {
> > > > connection.close();
> > > > }
> > > >
> > > > auditAction = (Audit)
> > > > ActionLoader.getInstance().getInstance("Audit");
> > > >
> > > > }
> > > >
> > > > public void testNoDataAvailable() throws Exception {
> > > >
> > > > // Add parameters to the RunData that will be used to login
> > > > a non existent user.
> > > > data.getParameters().setString("object_id", "636");
> > > > data.getParameters().setString("object_name", "workorder");
> > > > context.put("criteria", new
> > > > Criteria().add(WorkorderPeer.WORKORDER_ID, Integer.valueOf("636")));
> > > > context.put("followupURL", "www.sun.com");
> > > > auditAction.doPerform(data, context);
> > > > assertNotNull("Make sure we have an confirmation message.",
> > > > data.getMessages().getFormMessages("", "CONFIRM"));
> > > >
> > > > }
> > > >
> > > > Also, bump me your testcase and I'll look at it.
> > > >
> > > > Eric
> > > >
> > > > -----Original Message-----
> > > > From: Akmal Sarhan [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, March 11, 2003 7:00 AM
> > > > To: Turbine Users List
> > > > Subject: Re: Testing with maven/cactus
> > > >
> > > >
> > > > well, I have no problems using the classical way with cactus but
when
> I
> > > try
> > > > with maven I get this result:
> > > > Testsuite:
> de.byteaction.taskwatcher.test.modules.actions.TaskActionTest
> > > > Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0,42 sec
> > > >
> > > > Testcase: testDoTaketask took 0,39 sec
> > > > Caused an ERROR
> > > > Failed to get the test results. This is probably due to an error
that
> > > > happened on the server side when trying to execute the tests. Here
is
> > what
> > > > was returned by the server : [<html><head><title>Apache
> > > > Tomcat/4.1.18-LE-jdk14 - Error
report</title><STYLE><!--H1{font-family
> :
> > > > sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
> > > > H3{font-family : sans-serif,Arial,Tahoma;color :
> white;background-color
> > :
> > > > #0086b2;} BODY{font-family : sans-serif,Arial,Tahoma;color :
> > > > black;background-color : white;} B{color : white;background-color :
> > > > #0086b2;} HR{color : #0086b2;} --></STYLE> </head><body><h1>HTTP
> Status
> > > > 404 - /test/ServletRedirector</h1><HR size="1"
noshade><p><b>type</b>
> > > Status
> > > > report</p><p><b>message</b>
> > > > <u>/test/ServletRedirector</u></p><p><b>description</b> <u>The
> requested
> > > > resource (/test/ServletRedirector) is not available.</u></p><HR
> size="1"
> > > > noshade><h3>Apache Tomcat/4.1.18-LE-jdk14</h3></body></html>]
> > > > org.apache.cactus.util.ChainedRuntimeException: Failed to get the
test
> > > > results. This is probably due to an error that happened on the
server
> > side
> > > > when trying to execute the tests. Here is what was returned by the
> > server
> > > :
> > > > [<html><head><title>Apache Tomcat/4.1.18-LE-jdk14 - Error
> > > > report</title><STYLE><!--H1{font-family :
> sans-serif,Arial,Tahoma;color
> > :
> > > > white;background-color : #0086b2;} H3{font-family :
> > > > sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
> > > > BODY{font-family : sans-serif,Arial,Tahoma;color :
> > black;background-color
> > > :
> > > > white;} B{color : white;background-color : #0086b2;} HR{color :
> > > > #0086b2;} --></STYLE> </head><body><h1>HTTP Status 404 -
> > > > /test/ServletRedirector</h1><HR size="1" noshade><p><b>type</b>
Status
> > > > report</p><p><b>message</b>
> > > > <u>/test/ServletRedirector</u></p><p><b>description</b> <u>The
> requested
> > > > resource (/test/ServletRedirector) is not available.</u></p><HR
> size="1"
> > > > noshade><h3>Apache Tomcat/4.1.18-LE-jdk14</h3></body></html>]
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.dispatch2_doTest(AbstractHttpCli
> > > > ent.java;org/apache/cactus/util/log/LogAspect.aj(1k):120)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.around2_doTest(AbstractHttpClien
> > > > t.java;org/apache/cactus/util/log/LogAspect.aj(1k):1236)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpClient.java;o
> > > > rg/apache/cactus/util/log/LogAspect.aj(1k):104)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.AbstractWebTestCase.runGenericTest(AbstractWebTestCase.jav
> > > > a:260)
> > > > at
> org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133)
> > > > at
> > org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:195)
> > > > org.apache.cactus.client.ParsingException: Not a valid response
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.WebTestResultParser.readRootElement(WebTestResultPa
> > > > rser.java;org/apache/cactus/util/log/LogAspect.aj(1k):140)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.WebTestResultParser.dispatch29_parse(WebTestResultP
> > > > arser.java;org/apache/cactus/util/log/LogAspect.aj(1k):101)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.WebTestResultParser.around29_parse(WebTestResultPar
> > > > ser.java;org/apache/cactus/util/log/LogAspect.aj(1k):1236)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.WebTestResultParser.parse(WebTestResultParser.java;
> > > > org/apache/cactus/util/log/LogAspect.aj(1k):96)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.callGetResult(AbstractHttpClient
> > > > .java;org/apache/cactus/util/log/LogAspect.aj(1k):230)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.dispatch2_doTest(AbstractHttpCli
> > > > ent.java;org/apache/cactus/util/log/LogAspect.aj(1k):114)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.around2_doTest(AbstractHttpClien
> > > > t.java;org/apache/cactus/util/log/LogAspect.aj(1k):1236)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.client.AbstractHttpClient.doTest(AbstractHttpClient.java;o
> > > > rg/apache/cactus/util/log/LogAspect.aj(1k):104)
> > > > at
> > > >
> > >
> >
>
org.apache.cactus.AbstractWebTestCase.runGenericTest(AbstractWebTestCase.jav
> > > > a:260)
> > > > at
> org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:133)
> > > > at
> > org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:195)
> > > >
> > > > Testcase: testDoTaketask
> > > > ----- Original Message -----
> > > > From: <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Tuesday, March 11, 2003 12:01 PM
> > > > Subject: RE: Testing with maven/cactus
> > > >
> > > >
> > > > > Interesting. Can you send me a copy of your stack trace plus your
> > > cactus
> > > > > test? What app server are you using? Can you get the sample for
> the
> > > > plugin
> > > > > to run?
> > > > >
> > > > > Eric Pugh
> > > > >
> > > > > -----Original Message-----
> > > > > From: Akmal Sarhan [mailto:[EMAIL PROTECTED]
> > > > > Sent: Tuesday, March 11, 2003 2:47 AM
> > > > > To: [EMAIL PROTECTED]
> > > > > Subject: Testing with maven/cactus
> > > > >
> > > > >
> > > > > I am trying to get my tests running using cactus plugin for maven,
> but
> > > > > somehow I can not get it to work, has anyone tried this and if
yes,
> > > could
> > > > > you contribute a small howto(step by step) of what exactly should
be
> > > > changed
> > > > > to automate the tests
> > > > > I am using the CVS head of maven
> > > > > regards
> > > > > Akmal
> > > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > 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]
>
>
> ---------------------------------------------------------------------
> 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]
