----- Original Message -----
From: "Jim Cheesman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 18, 2001 8:51 AM
Subject: RE: Building Cactus
> At 06:52 PM 17/10/01, you wrote:
> >Thanks for sending this. In the future, please submit patches like this
as a
> >CVS diff as it makes our job a little easier. Also include the word
[PATCH]
> >in the subject line as it will help us spot them.
>
>
> Assuming:
> a) You have CVS installed
well, yes it is true that it is more difficult on windows as diff is not a
standard tool (BTW you don't need CVS, simply diff, which is part of cgywin
for example, or you can find it as an exe in several places).
> b) Presumably you need wewb access on the desktop (we have stand-alone
> workstations here with web access)...
I see what you mean. :(
>
>
> >In this case, there isn't an error, as the documentation for the method
in
> >question states:
> >
> > /**
> > * Test that the end method is called correctly when it's signature
> > * contains a <code>com.meterware.httpunit.WebResponse</code>
parameter.
> > *
> > * Note: We need the Httpunit jar and an XML parser jar on the
classpath
> > * for this test
> > */
>
>
> Yeah, but this doesn't build unless you have the old version of httpunit
> available - which may not be the case.
hum ... I'm not sure I believe this, for the following reasons :
A)
- cactus build is run every day by GUMP (seee
http://jakarta.apache.org/builds/gump/latest)
- htpunit is also built every day by GUMP from the latest CVS sources and
this is the version that is tested every day on Cactus
So I do believe Cactus is running with the latest version of httpunit every
day.
B) I'm running the latest httpunit version (1.2.6) on my machine and
everything is fine !
>
>
>
> (From the other mail)
> ><<
> >* There's an error in the image "Classpath.jpg" - it still refers
> >"commons-cactus.jar"
> >>>
> >I'm not sure I understand this one. What is the problem exactly?
>
> See attached. (And the images should really be gifs, not jpg.)
>
nope .... :)
See http://jakarta.apache.org/cactus/getting_started.html. It is fine. Now,
if you're running Cactus 1.1, that's normal you should see the old names in
the doc
>
>
>
> <<
> Where should cactus.properties go??? I've tried putting it everywhere!
> >>
> At the root of your classpath. For instance, if your packages commonly
start
> with com.cheesman you would want to put the cactus.properties next to the
> com directory.
>
>
>
> Tried that. (And what is the "root" of my classpath?) The problem still
occurs:
>
>
> d:\trabajos>java sinfo.rrm.RRMTestSuite
> [LocalConstants] C:\Documents and Settings\pc_ojcheesman.MSL\constants.ini
> .E.E.E
> Time: 0.04
> There were 3 errors:
> 1) testService(sinfo.rrm.TestGenerateServlet)
> java.lang.ExceptionInInitializerError: java.util.MissingResourceException:
> Can't find bundle for base name cactus, locale en_US
> at java.util.ResourceBundle.throwMissingResourceException(Unknown
> Source)
> at java.util.ResourceBundle.getBundleImpl(Unknown Source)
> at java.util.ResourceBundle.getBundle(Unknown Source)
> at
>
org.apache.cactus.client.AbstractHttpClient.<clinit>(AbstractHttpClient.java
:88)
> at
org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:130)
> at
> org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:371)
> at sinfo.rrm.RRMTestSuite.main(RRMTestSuite.java:50)
> 2) testDoGet(sinfo.rrm.TestExpirationServlet)
> java.lang.NoClassDefFoundError
> at
org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:130)
> at
> org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:371)
> at sinfo.rrm.RRMTestSuite.main(RRMTestSuite.java:50)
> 3) testDoGet(sinfo.rrm.TestBlockingServlet)
> java.lang.NoClassDefFoundError
> at
org.apache.cactus.ServletTestCase.runTest(ServletTestCase.java:130)
> at
> org.apache.cactus.AbstractTestCase.runBare(AbstractTestCase.java:371)
> at sinfo.rrm.RRMTestSuite.main(RRMTestSuite.java:50)
>
> FAILURES!!!
> Tests run: 3, Failures: 0, Errors: 3
>
>
> d:\trabajos>echo %CLASSPATH%
>
.;d:\classes;e:\jdk1.3\jdepend\lib\jdepend.jar;d:\bot\robocode\robocode.jar;
>
If this is your real classpath, then I don't see how you can run any Cactus
test, because it is missing cactus.jar, httpclient.jar, .... !! :)
Putting cactus.properties in _any_ directory mentioned in your classpath
will work (this is not a feature of cactus, it is how resource bundle works)
>
> I have a copy of cactus.properties in d:\classes. (And I've tried in .,
> jre/lib/ext, and when running under ant, in ANT_HOME/lib.) I've run out of
> places to stick the damn file! ;)
>
>
Thanks Jim
Hope everything is working for you now. Putting cactus.properties in
cactus.jar is definitely not the right place :)
-Vincent
