With thanks for Vincent by jove it has worked.
At last I can develop some test cases on Servlets
B.T.W in my company there are a few of se who are likely to be using Cactus so a
dedicated Cactus mailing group would be beneficial.
Cheers
Jon Belinfante
|--------+----------------------->
| | "Vincent |
| | Massol" |
| | <vmassol@octo|
| | .com> |
| | |
| | 23/05/01 |
| | 18:33 |
| | Please |
| | respond to |
| | jakarta-commo|
| | ns; Please |
| | respond to |
| | "Vincent |
| | Massol" |
| | |
|--------+----------------------->
>----------------------------------------------------------------------------|
| |
| To: [EMAIL PROTECTED] |
| cc: (bcc: Jon Belinfante/London/CWB) |
| Subject: Re: Cactus Configuration Problem |
>----------------------------------------------------------------------------|
ah ........
Since I started J2EEUnit (now known as Cactus) in November 2000, most (i.e.
99%) of the problems that have been reported were classpath problems ... So
I would say you have a 99% chance that your problem is a classpath problem.
More precisely it probably means that your test classes are not in the
server classpath.
Some information :
- read carefully the installation section on the Cactus web site. It says
what should be in the client classpath and what should be in the server
classpath.
- you do not need (and must not) to put anything in jre/lib/ext !
- you can package everything in a war file (that's how the Cactus samples
are run !), like this :
One way of doing it on the server side is to create a war file :
<mywebapp>/WEB-INF
|_ classes
|_ your classes under test (under the correct directory hierarchy)
|_ your test classes (under the correct directory hierarchy)
|_ lib
|_ commons-cactus.jar
|_ junit.jar
and just drop this war in <tomcat>/webapps.
Hope it helps.
Vincent.
----- Original Message -----
From: "Jon Belinfante" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 23, 2001 1:49 PM
Subject: RE: Cactus Configuration Problem
> I have now added the cactus.properties file to my Client classpath.
> I now have moved to next error which is
>
> 'java.lang.NoSuchMethodError: main
> Exception in thread main.
>
> I have followed the cactus example code ....
>
> Jon B.
>
>
>
> |--------+------------------------>
> | | Phil Magill |
> | | <phil.magill@p|
> | | hocis.com> |
> | | |
> | | 23/05/01 13:27|
> | | Please respond|
> | | to |
> | | jakarta-common|
> | | s |
> | | |
> |--------+------------------------>
>
>---------------------------------------------------------------------------
-|
> |
|
> | To: "'[EMAIL PROTECTED]'"
|
> | <[EMAIL PROTECTED]>
|
> | cc: (bcc: Jon Belinfante/London/CWB)
|
> | Subject: RE: Cactus Configuration Problem
|
>
>---------------------------------------------------------------------------
-|
>
>
>
>
> Jon
>
> Add the path to the cactus.properties file to your classpath and it should
> work.
>
> Thanks
>
> Phil
>
>
> -----Original Message-----
> From: Jon Belinfante [mailto:[EMAIL PROTECTED]]
> Sent: 23 May 2001 13:13
> To: [EMAIL PROTECTED]
> Subject: Cactus Configuration Problem
>
>
> Trying to configure Cactus with JBoss and Tomcat
>
> I am trying to run Cactus on a servlet and I keep getting the following
> error
> message
>
>
>
> java.lang.ExceptionInInitializerError: java.util.MissingResourceException:
> Can't
> find bundle for base name cactus, locale en_GB
>
> at
>
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:7
> 07)
>
> at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:679)
>
> at java.util.ResourceBundle.getBundle(ResourceBundle.java:546)
>
> at
>
org.apache.commons.cactus.client.AbstractHttpClient.<clinit>(AbstractHttpCli
> ent.java:82)
>
> at
>
org.apache.commons.cactus.ServletTestCase.runTest(ServletTestCase.java:128)
>
> at
>
org.apache.commons.cactus.AbstractTestCase.runBare(AbstractTestCase.java:266
> )
>
>
>
> I need help....
>
> Cheers
>
> Jon Belinfante
>
>
>
****************************************************************************
> **************************************************************************
> This e-mail has been prepared using information believed by the author
> to be reliable and accurate, but CWB makes no warranty as to accuracy
or
> completeness. In particular CWB does not accept responsibility for
> changes made to this e-mail after it was sent. Any opinions expressed
in
> this document are those of the author and do not necessarily reflect the
> opinions of the company or its affiliates. They may be subject to change
> without notice.
>
****************************************************************************
>
***************************************************************************
>
>
>
>
>
>
