----- Original Message ----- From: "Nicholas Lesiecki" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Vincent Massol" <[EMAIL PROTECTED]> Sent: Friday, September 28, 2001 5:09 PM Subject: RE: A day of discovery
> Yes, I should be able to update the docs (and change some exception handling > to provide more explicit errors as well.) However it's my wife's birthday > this weekend so it may be little while before I get to it. > Yes, please do not work on Cactus this week end as I wouldn't want your wife to hate us ... ! :-) WRT error handling, I had the idea at some point to write a configuration checker class that would verify that everything is set up correctly: cactus.properties in the classpath, correct jars in the classpath, .... and return nice and explicit error if it is not the case. I even started writing it and there is much room for improvement. I only wrote one class : ClientConfigurationChecker.java which will check configuration on the client side. It needs to be augmented. And it may be a good idea to do the same on the server side (and move from code from AbstractTestController.handleRequest() to a ServerConfigurationChecker class for example (see lines 137-152). > Cheers, > > nick > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 28, 2001 3:04 AM > To: [EMAIL PROTECTED] > Subject: Re: A day of discovery > > > > ----- Original Message ----- > From: "Nicholas Lesiecki" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "devel" <[EMAIL PROTECTED]> > Sent: Friday, September 28, 2001 12:25 AM > Subject: A day of discovery > > > > Hi, I just wanted to share something I discovered today with the Cactus > > users. It applies to Resin specifically (but it may apply to other servlet > > engines as well). That is: the cactus jar must be in the web-app's lib > > directory--it cannot be part of resin's global lib folder. The reason is > > that classes in the global lib directory cannot reference classes in the > > web-app's lib directory. This means when Cactus tries to instantiate your > > test class it will get a ClassNotFoundError. Putting the cactus jar on the > > same level as your test classes will solve this problem. > > > > Just an FYI. I checked the docs to see if I could find a reference to this > > issue, but I didn't see one immediately. Vincent has modified the docs > quite > > a bit recently, so I may have missed it. > > Well, that's something I had also discovered some time ago and which is why > that I have recommended everywhere to put all the jars in WEB-INF/lib. There > is also a description of what you discovered in the comment of the testwar > target in conf/sample/build/share/build-share.xml. However, you're right, it > should probably be better explained (that it is either all classes and jars > outside the webapp but then you don't usually benefit from class reloading > or everything inside teh webapp). > > Could you update the Getting Started Guide with that piece of information ? > > Thanks a lot > -Vincent > > > > > > > Cheers, > > > > Nick > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
