You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Sam Joseph <ga...@yha.att.ne.jp> on 2002/04/18 05:47:26 UTC
Problem with ServletInit and testSetAttribute in tests_tomcat_40
Hi,
So I'm trying to run the cactus samples on tomcat 4.0.3 and I'm having
some problems. I've been back and forwards through the docs a couple of
times so I think I have things set up correctly, and its almost working
but I get an error during start_tomcat_40
[java] StandardContext[/test]: Servlet /test has thrown a load()
exception: javax.servlet.ServletException: Servlet jsp'sServlet.init()
has thrown an exception
[java] javax.servlet.ServletException: Servlet jsp's Servlet.init()
has thrown asn exception
[java] at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935)
[java] at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808)
[java] at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3266)
[java] at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3395)
[java] at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
[java] ..........................
the tests then start and they go okay, but testSetAttribute gives an error
tests:
[junit] Running org.apache.cactus.TestAll
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559 sec
[junit] Testsuite: org.apache.cactus.TestAll
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559 sec
[junit]
[junit] Testcase: testLongProcess took 3.805 sec
[junit] Testcase: testLotsOfData took 2.494 sec
[junit] Testcase: testReadServletOutputStream took 0.15 sec
[junit] Testcase: testPostMethod took 0.03 sec
[junit] Testcase: testGetMethod took 0.03 sec
[junit] Testcase: testSetAttribute took 0.04 sec
[junit] Caused an ERROR
[junit] null
[junit] java.lang.NoSuchMethodError
[junit] at
org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1185)
[junit] at
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
[junit] at
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
[junit] at
org.apache.cactus.sample.SampleServlet.setSessionVariable(SampleServlet.java:119)
[junit] at
org.apache.cactus.sample.TestSampleServlet.testSetAttribute(TestSampleServlet.java:174)
[junit] at java.lang.reflect.Method.invoke(Native Method)
[junit] at
org.apache.cactus.AbstractTestCase.runServerTest(AbstractTestCase.java:491)
[junit] at
org.apache.cactus.AbstractTestCase.runBareServerTest(AbstractTestCase.java:456)
[junit] at
org.apache.cactus.server.AbstractTestCaller.doTest(AbstractTestCaller.java:137)
[junit] at
org.apache.cactus.server.AbstractTestController.handleRequest(AbstractTestController.java:122)
[junit] at
org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java:134)
[junit] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[junit] .................
And then tomcat shuts down without any other tests being run.
Can anybody help me out with this?
Thanks in advance.
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Vincent Massol wrote:
>
>>-----Original Message-----
>>
>>>
>>After re-reading the documentation again it seems clear that there are
>>
>2
>
>>JVMs at work here, and that I need to be careful to distinguish
>>classpaths for each of them, however my fundamental problem is that
>>while the documentation tells me to make sure that jars and paths are
>>
>in
>
>>the client side classpath or server side classpath, it is not clear
>>
>how
>
>>I set one or the other.
>>
>>I mean I know how to set a classpath, but last time I looked I has one
>>classpath in my programming environment,i.e.
>>
>>export CLASSPATH="%CLASSPATH:/blah/blah/blah"
>>
>>will set my one and only classpath. How can I set the clients and
>>server classpaths differently?
>>
>
>Sam,
>
>Yes, there are 2 JVMs : one that you start when you start the JUnit Test
>Runner and one that is started when you start your server. Again, you
>should read the Getting started guide
>(E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html). It
>explains *in detail* how you would configure your classpaths.
>
Well it might tell me in detail, but all it says is that I need to do
different things for my client-side and server-side classpaths. Now I
very well understand what client-side and server-side means, but there
is nothing I can see in this documentation that tells me how to set them
differently from one another, i.e. it just says
"you need to have the following jars and classes in your client side
classpath "
I mean I'm beginning to get the feeling that the client side classpath
is the one I set in the environment that I run cactus in, and that the
server side classpath is the one that is part of the webapp, but that is
by no means clear.
>However you said you were using the Samples as provided by Cactus. If it
>is the case you shouldn't touch anything at all.
>
Right, I've never tried to create my own application, I'm just trying to
run the sample, and it was running the sample that I got the original
error about ServletInit and testSetAttribute. You then told me to
re-read the documentation on getting started and on configuration that
seems to refer to testing one's own application, which I re-iterate I
have never tried to do.
I do hope you can help me solve this problem with *the sample
application*, because I would very much like to get it to run on my
computer.
Thanks in advance.
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 20 April 2002 14:30
> To: Cactus Users List
> Cc: Vincent Massol
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Sam Joseph wrote:
>
> > Vincent Massol wrote:
> >
> >> Sam,
> >>
> >> I think you should better read both :
> >>
> >> -
E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
> >> which explains how Cactus tests are packaged
> >>
> >> and
> >>
> >> - E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html
which
> >> explains how to configure your application web.xml.
> >>
> >> :-)
> >>
> >> Then, come back here and ask your question if something was not
clear
> >> from the documentation.
> >>
> > Well I've reread the documentation for the 3rd time but still feel
no
> > wiser.
>
> After re-reading the documentation again it seems clear that there are
2
> JVMs at work here, and that I need to be careful to distinguish
> classpaths for each of them, however my fundamental problem is that
> while the documentation tells me to make sure that jars and paths are
in
> the client side classpath or server side classpath, it is not clear
how
> I set one or the other.
>
> I mean I know how to set a classpath, but last time I looked I has one
> classpath in my programming environment,i.e.
>
> export CLASSPATH="%CLASSPATH:/blah/blah/blah"
>
> will set my one and only classpath. How can I set the clients and
> server classpaths differently?
>
Sam,
Yes, there are 2 JVMs : one that you start when you start the JUnit Test
Runner and one that is started when you start your server. Again, you
should read the Getting started guide
(E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html). It
explains *in detail* how you would configure your classpaths.
However you said you were using the Samples as provided by Cactus. If it
is the case you shouldn't touch anything at all.
> CHEERS> SAM
>
-Vincent
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Sam Joseph wrote:
> Vincent Massol wrote:
>
>> Sam,
>>
>> I think you should better read both :
>>
>> - E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
>> which explains how Cactus tests are packaged
>>
>> and
>>
>> - E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html which
>> explains how to configure your application web.xml.
>>
>> :-)
>>
>> Then, come back here and ask your question if something was not clear
>> from the documentation.
>>
> Well I've reread the documentation for the 3rd time but still feel no
> wiser.
After re-reading the documentation again it seems clear that there are 2
JVMs at work here, and that I need to be careful to distinguish
classpaths for each of them, however my fundamental problem is that
while the documentation tells me to make sure that jars and paths are in
the client side classpath or server side classpath, it is not clear how
I set one or the other.
I mean I know how to set a classpath, but last time I looked I has one
classpath in my programming environment,i.e.
export CLASSPATH="%CLASSPATH:/blah/blah/blah"
will set my one and only classpath. How can I set the clients and
server classpaths differently?
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
I can see only 3 solutions :
1/ Your have changed some Tomcat configuration file (where you installed
Tomcat), maybe a long time ago and it's causing this problem
or
2/ After you unzipped Jakarta-cactus-23-1.2.zip, you have changed
something other than build.properties, like web.xml found in
sample/conf/test
or
3/ Tomcat 4.0.3 does not work with Cactus 1.2 (I have never tested it
with Tomcat 4.0.x).
So here's what I propose : can you download the newest Cactus 1.3
(released last Sunday) and try with it ? Do exactly as you've done :
download the distrib + unzip + go into sample-servlet/build, create and
edit a build.properties file and type "ant test.all"
Note: The sample application build file does not work with Ant 1.4.1 (it
wasn't intentional but made it in the release). Simply comment out or
remove the line that says :
<fail message="Missing property or property pointing to an
invalid file (check your build.properties file)"
unless="properties.ok"/>
as it is only supported with Ant 1.5. Alternatively you can download and
use the prepackaged Ant that is available on the cactus web site.
Cheers,
-Vincent
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 23 April 2002 04:37
> To: Vincent Massol; cactus
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Hi Vincent
>
> Vincent Massol wrote:
>
> >Sam,
> >
> >Let's start again from the beginning ignoring everything we said in
our
> >previous email.
> >
> Sounds like a good idea.
>
> > The sample application is really very simple to get
> >started with.
> >
> So I've heard :-)
>
> >Let's start with some questions :
> >
> >1/ Do you have Ant installed ?
> >
> I do, version 1.4.1
>
> >Have you downloaded the prepackaged Ant
> >install from the Cactus web site ?
> >
> I have downloaded it, but I haven't unpacked or used it.
>
> >2/ Have you downloaded Tomcat and unzipped it in a directory ? (no
need
> >to configure anything at all) ?
> >
> A long time ago. I'm using tomcat 4.0.3
>
> >3/ What have you downloaded from Cactus web site (exact name of file)
?
> >
> jakarta-cactus-23-1.2.zip
>
> >4/ Have you unzipped it in a directory, let's say [CACTUS] ?
> >
> yes
>
> >5/ Have you created a [CACTUS]/build/build.properties (by copying and
> >editing [CACTUS]/build/build.properties.sample ?
> >
> yes
>
> >If answer to 3/ is yes, then you have finished. The only thing to do
is
> >to open a dos prompt, cd to [CACTUS]/build and type "ant tests_all"
> >
> right, that's what I did and I got the error that I originally sent
you
> in my first email:
>
> "its almost working but I get an error during start_tomcat_40"
>
> [java] StandardContext[/test]: Servlet /test has thrown a load()
> exception: javax.servlet.ServletException: Servlet jsp'sServlet.init()
> has thrown an exception
> [java] javax.servlet.ServletException: Servlet jsp's
Servlet.init()
> has thrown asn exception
> [java] at
>
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:
> 935)
>
> [java] at
>
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808)
> [java] at
>
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j
av
> a:3266)
>
> [java] at
>
org.apache.catalina.core.StandardContext.start(StandardContext.java:3395
)
> [java] at
>
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
> [java] ..........................
>
> "the tests then start and they go okay, but testSetAttribute gives an
> error"
>
> tests:
> [junit] Running org.apache.cactus.TestAll
> [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559
sec
> [junit] Testsuite: org.apache.cactus.TestAll
> [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559
sec
> [junit]
> [junit] Testcase: testLongProcess took 3.805 sec
> [junit] Testcase: testLotsOfData took 2.494 sec
> [junit] Testcase: testReadServletOutputStream took 0.15 sec
> [junit] Testcase: testPostMethod took 0.03 sec
> [junit] Testcase: testGetMethod took 0.03 sec
> [junit] Testcase: testSetAttribute took 0.04 sec
> [junit] Caused an ERROR
> [junit] null
> [junit] java.lang.NoSuchMethodError
> [junit] at
>
org.apache.catalina.session.StandardSession.setAttribute(StandardSession
.j
> ava:1185)
>
> [junit] at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardS
es
> sionFacade.java:191)
>
> [junit] at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardS
es
> sionFacade.java:191)
>
> [junit] at
>
org.apache.cactus.sample.SampleServlet.setSessionVariable(SampleServlet.
ja
> va:119)
>
> [junit] at
>
org.apache.cactus.sample.TestSampleServlet.testSetAttribute(TestSampleSe
rv
> let.java:174)
>
> [junit] at java.lang.reflect.Method.invoke(Native Method)
> [junit] at
>
org.apache.cactus.AbstractTestCase.runServerTest(AbstractTestCase.java:4
91
> )
> [junit] at
>
org.apache.cactus.AbstractTestCase.runBareServerTest(AbstractTestCase.ja
va
> :456)
>
> [junit] at
>
org.apache.cactus.server.AbstractTestCaller.doTest(AbstractTestCaller.ja
va
> :137)
>
> [junit] at
>
org.apache.cactus.server.AbstractTestController.handleRequest(AbstractTe
st
> Controller.java:122)
>
> [junit] at
>
org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirec
to
> r.java:134)
>
> [junit] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> [junit] .................
>
>
> "And then tomcat shuts down without any other tests being run."
>
> Any help will be greatly appreciated.
>
> CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Hi Vincent
Vincent Massol wrote:
>Sam,
>
>Let's start again from the beginning ignoring everything we said in our
>previous email.
>
Sounds like a good idea.
> The sample application is really very simple to get
>started with.
>
So I've heard :-)
>Let's start with some questions :
>
>1/ Do you have Ant installed ?
>
I do, version 1.4.1
>Have you downloaded the prepackaged Ant
>install from the Cactus web site ?
>
I have downloaded it, but I haven't unpacked or used it.
>2/ Have you downloaded Tomcat and unzipped it in a directory ? (no need
>to configure anything at all) ?
>
A long time ago. I'm using tomcat 4.0.3
>3/ What have you downloaded from Cactus web site (exact name of file) ?
>
jakarta-cactus-23-1.2.zip
>4/ Have you unzipped it in a directory, let's say [CACTUS] ?
>
yes
>5/ Have you created a [CACTUS]/build/build.properties (by copying and
>editing [CACTUS]/build/build.properties.sample ?
>
yes
>If answer to 3/ is yes, then you have finished. The only thing to do is
>to open a dos prompt, cd to [CACTUS]/build and type "ant tests_all"
>
right, that's what I did and I got the error that I originally sent you
in my first email:
"its almost working but I get an error during start_tomcat_40"
[java] StandardContext[/test]: Servlet /test has thrown a load()
exception: javax.servlet.ServletException: Servlet jsp'sServlet.init()
has thrown an exception
[java] javax.servlet.ServletException: Servlet jsp's Servlet.init()
has thrown asn exception
[java] at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935)
[java] at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808)
[java] at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3266)
[java] at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3395)
[java] at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
[java] ..........................
"the tests then start and they go okay, but testSetAttribute gives an error"
tests:
[junit] Running org.apache.cactus.TestAll
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559 sec
[junit] Testsuite: org.apache.cactus.TestAll
[junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559 sec
[junit]
[junit] Testcase: testLongProcess took 3.805 sec
[junit] Testcase: testLotsOfData took 2.494 sec
[junit] Testcase: testReadServletOutputStream took 0.15 sec
[junit] Testcase: testPostMethod took 0.03 sec
[junit] Testcase: testGetMethod took 0.03 sec
[junit] Testcase: testSetAttribute took 0.04 sec
[junit] Caused an ERROR
[junit] null
[junit] java.lang.NoSuchMethodError
[junit] at
org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1185)
[junit] at
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
[junit] at
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:191)
[junit] at
org.apache.cactus.sample.SampleServlet.setSessionVariable(SampleServlet.java:119)
[junit] at
org.apache.cactus.sample.TestSampleServlet.testSetAttribute(TestSampleServlet.java:174)
[junit] at java.lang.reflect.Method.invoke(Native Method)
[junit] at
org.apache.cactus.AbstractTestCase.runServerTest(AbstractTestCase.java:491)
[junit] at
org.apache.cactus.AbstractTestCase.runBareServerTest(AbstractTestCase.java:456)
[junit] at
org.apache.cactus.server.AbstractTestCaller.doTest(AbstractTestCaller.java:137)
[junit] at
org.apache.cactus.server.AbstractTestController.handleRequest(AbstractTestController.java:122)
[junit] at
org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java:134)
[junit] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
[junit] .................
"And then tomcat shuts down without any other tests being run."
Any help will be greatly appreciated.
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
Let's start again from the beginning ignoring everything we said in our
previous email. The sample application is really very simple to get
started with.
Let's start with some questions :
1/ Do you have Ant installed ? Have you downloaded the prepackaged Ant
install from the Cactus web site ?
2/ Have you downloaded Tomcat and unzipped it in a directory ? (no need
to configure anything at all) ?
3/ What have you downloaded from Cactus web site (exact name of file) ?
4/ Have you unzipped it in a directory, let's say [CACTUS] ?
5/ Have you created a [CACTUS]/build/build.properties (by copying and
editing [CACTUS]/build/build.properties.sample ?
If answer to 3/ is yes, then you have finished. The only thing to do is
to open a dos prompt, cd to [CACTUS]/build and type "ant tests_all"
Thanks
-Vincent
BTW, this is what is on
http://jakarta.apache.org/cactus/howto_sample.html. This is the only
information to read if you just want to run the Sample application
without understanding how it works.
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 21 April 2002 05:43
> To: Cactus Users List
> Cc: sam@neurogrid.com
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Vincent Massol wrote:
>
> >Sam,
> >
> >>-----Original Message-----
> >>From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> >>Sent: 20 April 2002 14:16
> >>To: Vincent Massol; cactus
> >>Subject: Re: Problem with ServletInit and testSetAttribute in
> >>tests_tomcat_40
> >>
> >>Vincent Massol wrote:
> >>
> >>>Sam,
> >>>
> >>>I think you should better read both :
> >>>
> >>>-
E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
> >>>which explains how Cactus tests are packaged
> >>>
> >>>and
> >>>
> >>>- E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html
> >>>
> >which
> >
> >>>explains how to configure your application web.xml.
> >>>
> >>>:-)
> >>>
> >>>Then, come back here and ask your question if something was not
clear
> >>>
> >>>from the documentation.
> >>
> >>Well I've reread the documentation for the 3rd time but still feel
no
> >>wiser.
> >>
> >
> >Oops. :-(. Actually that's quite interesting as you could help us
make
> >it more clear ... :-)
> >
> I'd love to help you.
>
> >
> >
> >>In the first instance I am confused why I should need to edit the
> >>web.xml files in a sample that comes prepackaged with cactus.
> >>
> >
> >Answer is no you don't need to edit anything. Can you tell me where
does
> >it say you need to do this ?
> >
> It doesn't. I assumed that I needed to because in response to my
query
> about running the sample application you told me to re-read the files
> that told me how to edit my web.xml. Since you were answering my
> question about how to solve an error occuring from the sample
> application, I assumed that when you told me to read a document that
> would describe how to edit my web.xml file, that I needed to edit my
> web.xml file.
>
> >If you want to run the samples then simply
> >read the Samples Howto on the web site
> >(E:\Dev\jakarta-cactus\documentation\dist\doc\howto_sample.html).
> >
> Yes, I've also read this several times. I have only ever been trying
to
> run the sample
>
> >>I mean
> >>surely the sample is a fixed thing, why do I need to reconfigure the
> >>web.xml regarding information that is intrinsic to the existing
> >>
> >sample?
> >
> the sample application that you gusy provide for testing cactus.
>
> >
> >>Why can't it just be configured already?
> >>
> >it is.
> >
> Jolly good. Then I am confused as to why you recommended me to read a
> document about reconfiguring my web.xml in order to fix an error
arising
> from me trying to run your sample application.
>
> >You're mixing 2 things :
> >- the preconfigured sample for which you don't need to touch anything
> >apart from editing its build.properties file
> >- the way to configure cactus for your own webapp.
> >
> okay, so I don't have my own webapp at the moment, as I hope is
becoming
> clear
>
> >In any case, there is only one web.xml that is important, it is the
one
> >you're using to run your application. The sample application is a
full
> >fledged application and it is why there are 2 web.xml : one that is
the
> >one without the tests, when you want to deliver your application and
one
> >for testing (i.e. the one that includes Cactus mappings).
> >
> >Feel free to send some documentation patches to improve the Web site
> >documentation for places when you think it is not clear.
> >
> I will hope to do so, once I understand why the sample application is
> not working.
>
> >><snip>error</snip>
> >>
> >
> >I don't see anything related to Cactus in this startup error. Maybe
you
> >should post to the Tomcat mailing list because I think you've got
> >something wrong in your Tomcat web.xml. The easiest way to solve it
is
> >to re-download Tomcat and unzip it (that's all it needs).
> >
> no this error is not related to cactus. I added it as an example of
the
> errors I was getting when I tried to edit the sample application
web.xml
> file, which from your first email is what I thought you wanted me to
do.
>
> I think I would like to clear at least one thing up, which is this.
>
> Do I need to place the sample application in my tomcat webapps
> directory, or am I supposed to place it my cactus root directory, or
> somewhere completely separate. This would appear to be unclear from
the
> sample howto document:
>
> http://jakarta.apache.org/cactus/howto_sample.html
>
> Thanks in advance.
>
> CHEERS> SAM
>
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Vincent Massol wrote:
>Sam,
>
>>-----Original Message-----
>>From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
>>Sent: 20 April 2002 14:16
>>To: Vincent Massol; cactus
>>Subject: Re: Problem with ServletInit and testSetAttribute in
>>tests_tomcat_40
>>
>>Vincent Massol wrote:
>>
>>>Sam,
>>>
>>>I think you should better read both :
>>>
>>>- E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
>>>which explains how Cactus tests are packaged
>>>
>>>and
>>>
>>>- E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html
>>>
>which
>
>>>explains how to configure your application web.xml.
>>>
>>>:-)
>>>
>>>Then, come back here and ask your question if something was not clear
>>>
>>>from the documentation.
>>
>>Well I've reread the documentation for the 3rd time but still feel no
>>wiser.
>>
>
>Oops. :-(. Actually that's quite interesting as you could help us make
>it more clear ... :-)
>
I'd love to help you.
>
>
>>In the first instance I am confused why I should need to edit the
>>web.xml files in a sample that comes prepackaged with cactus.
>>
>
>Answer is no you don't need to edit anything. Can you tell me where does
>it say you need to do this ?
>
It doesn't. I assumed that I needed to because in response to my query
about running the sample application you told me to re-read the files
that told me how to edit my web.xml. Since you were answering my
question about how to solve an error occuring from the sample
application, I assumed that when you told me to read a document that
would describe how to edit my web.xml file, that I needed to edit my
web.xml file.
>If you want to run the samples then simply
>read the Samples Howto on the web site
>(E:\Dev\jakarta-cactus\documentation\dist\doc\howto_sample.html).
>
Yes, I've also read this several times. I have only ever been trying to
run the sample
>>I mean
>>surely the sample is a fixed thing, why do I need to reconfigure the
>>web.xml regarding information that is intrinsic to the existing
>>
>sample?
>
the sample application that you gusy provide for testing cactus.
>
>>Why can't it just be configured already?
>>
>it is.
>
Jolly good. Then I am confused as to why you recommended me to read a
document about reconfiguring my web.xml in order to fix an error arising
from me trying to run your sample application.
>You're mixing 2 things :
>- the preconfigured sample for which you don't need to touch anything
>apart from editing its build.properties file
>- the way to configure cactus for your own webapp.
>
okay, so I don't have my own webapp at the moment, as I hope is becoming
clear
>In any case, there is only one web.xml that is important, it is the one
>you're using to run your application. The sample application is a full
>fledged application and it is why there are 2 web.xml : one that is the
>one without the tests, when you want to deliver your application and one
>for testing (i.e. the one that includes Cactus mappings).
>
>Feel free to send some documentation patches to improve the Web site
>documentation for places when you think it is not clear.
>
I will hope to do so, once I understand why the sample application is
not working.
>><snip>error</snip>
>>
>
>I don't see anything related to Cactus in this startup error. Maybe you
>should post to the Tomcat mailing list because I think you've got
>something wrong in your Tomcat web.xml. The easiest way to solve it is
>to re-download Tomcat and unzip it (that's all it needs).
>
no this error is not related to cactus. I added it as an example of the
errors I was getting when I tried to edit the sample application web.xml
file, which from your first email is what I thought you wanted me to do.
I think I would like to clear at least one thing up, which is this.
Do I need to place the sample application in my tomcat webapps
directory, or am I supposed to place it my cactus root directory, or
somewhere completely separate. This would appear to be unclear from the
sample howto document:
http://jakarta.apache.org/cactus/howto_sample.html
Thanks in advance.
CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 20 April 2002 14:16
> To: Vincent Massol; cactus
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Vincent Massol wrote:
>
> >Sam,
> >
> >I think you should better read both :
> >
> >- E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
> >which explains how Cactus tests are packaged
> >
> >and
> >
> >- E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html
which
> >explains how to configure your application web.xml.
> >
> >:-)
> >
> >Then, come back here and ask your question if something was not clear
> >from the documentation.
> >
> Well I've reread the documentation for the 3rd time but still feel no
> wiser.
Oops. :-(. Actually that's quite interesting as you could help us make
it more clear ... :-)
>
> In the first instance I am confused why I should need to edit the
> web.xml files in a sample that comes prepackaged with cactus.
Answer is no you don't need to edit anything. Can you tell me where does
it say you need to do this ? If you want to run the samples then simply
read the Samples Howto on the web site
(E:\Dev\jakarta-cactus\documentation\dist\doc\howto_sample.html).
> I mean
> surely the sample is a fixed thing, why do I need to reconfigure the
> web.xml regarding information that is intrinsic to the existing
sample?
> Why can't it just be configured already?
>
it is.
> I can't see anything in the documents that says I need to change the
> web.xml file in my actual tomcat distribution, so I haven't tried that
> assuming that I need to make some modifications to the three different
> web.xml files in the sample/conf/ sample/conf/test/ and
> sample/conf/test/tomcat40
>
that's right.
> I have identified that the main web.xml that is being accessed from
> sample/conf/test/ and that the sample/conf/test/tomcat40/ web.xml is
> also required to be "added" I have tried various combinations of
placing
> the web.xml file described in
> D:\jakarta-cactus-23-1.2\doc\howto_config.html in both of these
places,
> in either, combining it with the existing web.xml that was in these
> locations originally, and so forth. I have not improved upon my
original
> error and now have new ones such as the one appended below.
>
> I would say that at least three things are unclear from your
> documentation.
>
> 1. Which web.xml file I am supposed to be editing?
> 2. Am I supposed to add the example web.xml to the existing ones or
> replace them?
> 3. Am I supposed to be taking this package and placing it in my tomcat
> webapps, and modifying a web.xml file over there?
>
> Any help will be greatly appreciated.
>
> CHEERS> SAM
>
You're mixing 2 things :
- the preconfigured sample for which you don't need to touch anything
apart from editing its build.properties file
- the way to configure cactus for your own webapp.
In any case, there is only one web.xml that is important, it is the one
you're using to run your application. The sample application is a full
fledged application and it is why there are 2 web.xml : one that is the
one without the tests, when you want to deliver your application and one
for testing (i.e. the one that includes Cactus mappings).
Feel free to send some documentation patches to improve the Web site
documentation for places when you think it is not clear.
>
>
> [excuse the illegible characters, my operating system is japanese]
>
> start_tomcat_40:
> [java] HttpConnector ???????IP????????????????????
> [java] ???? Tomcat-Standalone ??????
> [java] Apache Tomcat/4.0.3
> [java] StandardHost[localhost]: URL
> jar:file:D:\jakarta-cactus-23-
> 1.2\sample\target\test\tomcat40\webapps\test.war!/
> ?????????? /test ?Web??????????????????
> [java] WebappLoader[/test]: ?????????????????
> D:\jakarta-tomcat-4.0.3\work\localhost\test ??????
> [java] WebappLoader[/test]: JAR /WEB-INF/lib/cactus.jar ?
> D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-
> INF\lib\cactus.jar
> ??????
> [java] WebappLoader[/test]: JAR /WEB-INF/lib/httpclient.jar ?
> D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-
> INF\lib\httpclient.jar
> ??????
> [java] WebappLoader[/test]: JAR /WEB-INF/lib/junit.jar ?
> D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-
> INF\lib\junit.jar
> ??????
> [java] WebappLoader[/test]: JAR /WEB-INF/lib/log4j.jar ?
> D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-
> INF\lib\log4j.jar
> ??????
> [java] StandardManager[/test]: ????????? java.security.SecureRandom
> ????????????
> [java] StandardManager[/test]: ???????????????????
> [java] ERROR reading java.io.ByteArrayInputStream@1f2ee1
> [java] At Line 38 /web-app/servlet/
> [java]
> [java] ContextConfig[/test]: ?????????web.xml????????
> [java] java.lang.IllegalArgumentException: addChild: Child name 'jsp'
is
> not unique
> [java] java.lang.IllegalArgumentException: addChild: Child name 'jsp'
is
> not unique
> [java] at
>
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> [java] at
>
org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1
27
> 6)
> [java] at java.lang.reflect.Method.invoke(Native Method)
> [java] at
org.apache.catalina.util.xml.AddChild.end(XmlMapper.java:811)
> [java] at
> org.apache.catalina.util.xml.XmlMapper.matchEnd(XmlMapper.java:419)
> [java] at
> org.apache.catalina.util.xml.XmlMapper.endElement(XmlMapper.java:119)
> [java] at
>
org.xml.sax.helpers.XMLReaderAdapter.endElement(XMLReaderAdapter.java:34
7)
> [java] at
> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1523)
> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
> [java] at
> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
> [java] at
> org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
> [java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
> [java] at
> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
> [java] at
> org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
> [java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:326)
> [java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:101)
> [java] at
> org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:275)
> [java] at
>
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfi
g.
> java:256)
>
>
>
I don't see anything related to Cactus in this startup error. Maybe you
should post to the Tomcat mailing list because I think you've got
something wrong in your Tomcat web.xml. The easiest way to solve it is
to re-download Tomcat and unzip it (that's all it needs).
-Vincent
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Vincent Massol wrote:
>Sam,
>
>I think you should better read both :
>
>- E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
>which explains how Cactus tests are packaged
>
>and
>
>- E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html which
>explains how to configure your application web.xml.
>
>:-)
>
>Then, come back here and ask your question if something was not clear
>from the documentation.
>
Well I've reread the documentation for the 3rd time but still feel no
wiser.
In the first instance I am confused why I should need to edit the
web.xml files in a sample that comes prepackaged with cactus. I mean
surely the sample is a fixed thing, why do I need to reconfigure the
web.xml regarding information that is intrinsic to the existing sample?
Why can't it just be configured already?
I can't see anything in the documents that says I need to change the
web.xml file in my actual tomcat distribution, so I haven't tried that
assuming that I need to make some modifications to the three different
web.xml files in the sample/conf/ sample/conf/test/ and
sample/conf/test/tomcat40
I have identified that the main web.xml that is being accessed from
sample/conf/test/ and that the sample/conf/test/tomcat40/ web.xml is
also required to be "added" I have tried various combinations of placing
the web.xml file described in
D:\jakarta-cactus-23-1.2\doc\howto_config.html in both of these places,
in either, combining it with the existing web.xml that was in these
locations originally, and so forth. I have not improved upon my original
error and now have new ones such as the one appended below.
I would say that at least three things are unclear from your documentation.
1. Which web.xml file I am supposed to be editing?
2. Am I supposed to add the example web.xml to the existing ones or
replace them?
3. Am I supposed to be taking this package and placing it in my tomcat
webapps, and modifying a web.xml file over there?
Any help will be greatly appreciated.
CHEERS> SAM
[excuse the illegible characters, my operating system is japanese]
start_tomcat_40:
[java] HttpConnector ???????IP????????????????????
[java] ???? Tomcat-Standalone ??????
[java] Apache Tomcat/4.0.3
[java] StandardHost[localhost]: URL
jar:file:D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test.war!/
?????????? /test ?Web??????????????????
[java] WebappLoader[/test]: ?????????????????
D:\jakarta-tomcat-4.0.3\work\localhost\test ??????
[java] WebappLoader[/test]: JAR /WEB-INF/lib/cactus.jar ?
D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-INF\lib\cactus.jar
??????
[java] WebappLoader[/test]: JAR /WEB-INF/lib/httpclient.jar ?
D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-INF\lib\httpclient.jar
??????
[java] WebappLoader[/test]: JAR /WEB-INF/lib/junit.jar ?
D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-INF\lib\junit.jar
??????
[java] WebappLoader[/test]: JAR /WEB-INF/lib/log4j.jar ?
D:\jakarta-cactus-23-1.2\sample\target\test\tomcat40\webapps\test\WEB-INF\lib\log4j.jar
??????
[java] StandardManager[/test]: ????????? java.security.SecureRandom
????????????
[java] StandardManager[/test]: ???????????????????
[java] ERROR reading java.io.ByteArrayInputStream@1f2ee1
[java] At Line 38 /web-app/servlet/
[java]
[java] ContextConfig[/test]: ?????????web.xml????????
[java] java.lang.IllegalArgumentException: addChild: Child name 'jsp' is
not unique
[java] java.lang.IllegalArgumentException: addChild: Child name 'jsp' is
not unique
[java] at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
[java] at
org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1276)
[java] at java.lang.reflect.Method.invoke(Native Method)
[java] at org.apache.catalina.util.xml.AddChild.end(XmlMapper.java:811)
[java] at
org.apache.catalina.util.xml.XmlMapper.matchEnd(XmlMapper.java:419)
[java] at
org.apache.catalina.util.xml.XmlMapper.endElement(XmlMapper.java:119)
[java] at
org.xml.sax.helpers.XMLReaderAdapter.endElement(XMLReaderAdapter.java:347)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1523)
[java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
[java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
[java] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
[java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
[java] at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
[java] at
org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
[java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:326)
[java] at javax.xml.parsers.SAXParser.parse(SAXParser.java:101)
[java] at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:275)
[java] at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:256)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
I think you should better read both :
- E:\Dev\jakarta-cactus\documentation\dist\doc\getting_started.html,
which explains how Cactus tests are packaged
and
- E:\Dev\jakarta-cactus\documentation\dist\doc\howto_config.html which
explains how to configure your application web.xml.
:-)
Then, come back here and ask your question if something was not clear
from the documentation.
Thanks
Cheers,
-Vincent
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 20 April 2002 12:23
> To: Cactus Users List
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Vincent Massol wrote:
>
> >Sam,
> >
> >You need to declare and map Cactus redirectors in your webapp web.xml
as
> >is described on http://jakarta.apache.org/cactus/howto_config.html
> >
> >However, I don't think you've sent me the web.xml that you're really
> >using as 6 tests were running fine and without the Cactus redirector
> >none should have worked at all.
> >
> oops.
>
> Yeah, wrong file, here's the correct one. Or at least the one in the
> sample/conf/test/tomcat40/ directory which I assume is the one being
> used since I am only testing on tomcat.
>
> CHEERS> SAM
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Vincent Massol wrote:
>Sam,
>
>You need to declare and map Cactus redirectors in your webapp web.xml as
>is described on http://jakarta.apache.org/cactus/howto_config.html
>
>However, I don't think you've sent me the web.xml that you're really
>using as 6 tests were running fine and without the Cactus redirector
>none should have worked at all.
>
oops.
Yeah, wrong file, here's the correct one. Or at least the one in the
sample/conf/test/tomcat40/ directory which I assume is the one being
used since I am only testing on tomcat.
CHEERS> SAM
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
You need to declare and map Cactus redirectors in your webapp web.xml as
is described on http://jakarta.apache.org/cactus/howto_config.html
However, I don't think you've sent me the web.xml that you're really
using as 6 tests were running fine and without the Cactus redirector
none should have worked at all.
Thanks
-Vincent
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 20 April 2002 11:54
> To: Cactus Users List
> Subject: Re: Problem with ServletInit and testSetAttribute in
> tests_tomcat_40
>
> Hi Vincent,
>
> I have attached the web.xml document from the sample/conf/directory.
>
> It appears rather bare. Is there something I was supposed to put in
it?
> Apologies if I have overlooked something obvious.
>
> Thanks in advance.
>
> CHEERS> SAM
>
> Vincent Massol wrote:
>
> >Sam,
> >
> >Strange. Can you send us your web.xml ? I don't see anything wrong
with
> >Cactus in your stack trace. Looks like there is something else.
> >
> >-Vincent
> >
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Sam Joseph <ga...@yha.att.ne.jp>.
Hi Vincent,
I have attached the web.xml document from the sample/conf/directory.
It appears rather bare. Is there something I was supposed to put in it?
Apologies if I have overlooked something obvious.
Thanks in advance.
CHEERS> SAM
Vincent Massol wrote:
>Sam,
>
>Strange. Can you send us your web.xml ? I don't see anything wrong with
>Cactus in your stack trace. Looks like there is something else.
>
>-Vincent
>
RE: Problem with ServletInit and testSetAttribute in tests_tomcat_40
Posted by Vincent Massol <vm...@octo.com>.
Sam,
Strange. Can you send us your web.xml ? I don't see anything wrong with
Cactus in your stack trace. Looks like there is something else.
-Vincent
> -----Original Message-----
> From: Sam Joseph [mailto:gaijin@yha.att.ne.jp]
> Sent: 18 April 2002 04:47
> To: cactus-user@jakarta.apache.org
> Subject: Problem with ServletInit and testSetAttribute in
tests_tomcat_40
>
> Hi,
>
> So I'm trying to run the cactus samples on tomcat 4.0.3 and I'm having
> some problems. I've been back and forwards through the docs a couple
of
> times so I think I have things set up correctly, and its almost
working
> but I get an error during start_tomcat_40
>
> [java] StandardContext[/test]: Servlet /test has thrown a load()
> exception: javax.servlet.ServletException: Servlet jsp'sServlet.init()
> has thrown an exception
> [java] javax.servlet.ServletException: Servlet jsp's
Servlet.init()
> has thrown asn exception
> [java] at
>
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:
> 935)
> [java] at
>
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808)
> [java] at
>
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j
av
> a:3266)
> [java] at
>
org.apache.catalina.core.StandardContext.start(StandardContext.java:3395
)
> [java] at
>
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
> [java] ..........................
>
> the tests then start and they go okay, but testSetAttribute gives an
error
>
> tests:
> [junit] Running org.apache.cactus.TestAll
> [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559
sec
> [junit] Testsuite: org.apache.cactus.TestAll
> [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 6.559
sec
> [junit]
> [junit] Testcase: testLongProcess took 3.805 sec
> [junit] Testcase: testLotsOfData took 2.494 sec
> [junit] Testcase: testReadServletOutputStream took 0.15 sec
> [junit] Testcase: testPostMethod took 0.03 sec
> [junit] Testcase: testGetMethod took 0.03 sec
> [junit] Testcase: testSetAttribute took 0.04 sec
> [junit] Caused an ERROR
> [junit] null
> [junit] java.lang.NoSuchMethodError
> [junit] at
>
org.apache.catalina.session.StandardSession.setAttribute(StandardSession
.j
> ava:1185)
> [junit] at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardS
es
> sionFacade.java:191)
> [junit] at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardS
es
> sionFacade.java:191)
> [junit] at
>
org.apache.cactus.sample.SampleServlet.setSessionVariable(SampleServlet.
ja
> va:119)
> [junit] at
>
org.apache.cactus.sample.TestSampleServlet.testSetAttribute(TestSampleSe
rv
> let.java:174)
> [junit] at java.lang.reflect.Method.invoke(Native Method)
> [junit] at
>
org.apache.cactus.AbstractTestCase.runServerTest(AbstractTestCase.java:4
91
> )
> [junit] at
>
org.apache.cactus.AbstractTestCase.runBareServerTest(AbstractTestCase.ja
va
> :456)
> [junit] at
>
org.apache.cactus.server.AbstractTestCaller.doTest(AbstractTestCaller.ja
va
> :137)
> [junit] at
>
org.apache.cactus.server.AbstractTestController.handleRequest(AbstractTe
st
> Controller.java:122)
> [junit] at
>
org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirec
to
> r.java:134)
> [junit] at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> [junit] .................
>
>
> And then tomcat shuts down without any other tests being run.
>
> Can anybody help me out with this?
>
> Thanks in advance.
>
> CHEERS> SAM
>
>
> --
> To unsubscribe, e-mail: <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.351 / Virus Database: 197 - Release Date: 19/04/2002
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>