> > > > 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 !
I'm downloading it now - and hopefully that should help. > > > > > > > > (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 D:\java\jakarta-cactus-23-1.2\doc\getting_started.html (directly extracted from the binary zip jakarta-cactus-23-1.2.zip) Classpath.jpg shows commons-cactus.jar. > > > > > > > > << > > 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. Doesn't work. d:\classes is definitely in my classpath, definitely exists, definitely has a copy of cactus.properties in it, and definitely doesn't work (until I add it manually to the 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, .... !! :) That's what the ext directory is for - I was of the understanding that CLASSPATH as a feature of the environment was being deprecated, and that in the future everything would be more dynamic... >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) Should be, I agree - but it seems a little buggy to me. (For example, I've found that tomcat doesn't recognise resource bundles unless they are in a jar...) > > > > 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 :) Still, it works. That'll do for me for now ;) -- * Jim Cheesman * Trabajo: [EMAIL PROTECTED] - (34)(91) 724 9200 x 2360 Ambivalent? Well, yes and no.
