Return-Path: Mailing-List: contact watchdog-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list watchdog-dev@jakarta.apache.org Delivered-To: moderator for watchdog-dev@jakarta.apache.org Received: (qmail 10597 invoked from network); 18 Oct 2000 18:32:26 -0000 Received: from mercury.sun.com (192.9.25.1) by locus.apache.org with SMTP; 18 Oct 2000 18:32:26 -0000 Received: from shorter.eng.sun.com ([129.144.252.35]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA17617 for ; Wed, 18 Oct 2000 11:32:26 -0700 (PDT) Received: from woofer (woofer [129.144.250.167]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with SMTP id LAA29596 for ; Wed, 18 Oct 2000 11:32:25 -0700 (PDT) Message-Id: <200010181832.LAA29596@shorter.eng.sun.com> Date: Wed, 18 Oct 2000 11:32:40 -0700 (PDT) From: "Santosh Singh [TEMP]" Reply-To: "Santosh Singh [TEMP]" Subject: Re: Watchdog and Jetty3 To: watchdog-dev@jakarta.apache.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: pi2HRW6OoJbtg5BdFgJhAw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi All, I joined the "watchdog " group recently and i'll be the primary source of contact for all watchdog related issues,discussions etc. All the recommendations,suggestions are welcome. We have created a new branch for watchdog with the name watchdog-4.0 . This will have tests for Servlet 2.3/Jsp1.2 specs. Right now it is mainly a much better version of previous watchdog source code.I would recommend using it once it becomes available for download. Thanks, Santosh > Mailing-List: contact watchdog-dev-help@jakarta.apache.org; run by ezmlm > list-help: > list-unsubscribe: > list-post: > Delivered-To: mailing list watchdog-dev@jakarta.apache.org > X-Accept-Language: en > MIME-Version: 1.0 > To: watchdog-dev@jakarta.apache.org > CC: jetty-discuss@egroups.com > Subject: Watchdog and Jetty3 > Content-Transfer-Encoding: 7bit > X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > > Hi watchdog developers. > > I'm currently using watchdog to test Jetty3 for 2.2 servlet compliance. > I'm using the CVS snapshot from 17 Oct > > Firstly a small bug report: > > In org/apache/tools/moo/servlet/ServletTest.java > The sos variable is set after the doTest method. > Thus if the doTest throws an exception the props.put fails as sos is > null. Simple fix is to set sos before calling doTest (or test > a container that never fails :-) > > > Of the 9 tests that I'm currently failing, one of them is: > org.apache.jcheck.servlet.client.javax_servlet.ServletContext.GetContextTest > > where you appear to try to get the following context: > /servlet/tests.javax_servlet.ServletContext.GetServletContextTestServlet > > > This appears to be a path within the scope of the current context. My reading > of the spec and java doc is that this method is used to get other contexts > and thus should be passed a uri INCLUDING the context. From the javadoc: > > /** > * Returns a ServletContext object that > * corresponds to a specified URL on the server. > * > *

This method allows servlets to gain > * access to the context for various parts of the server, and as > * needed obtain {@link RequestDispatcher} objects from the context. > * The given path must be absolute (beginning with "/") and is > * interpreted based on the server's document root. > * > *

In a security conscious environment, the servlet container may > * return null for a given URL. > * > * @param uripath a String specifying the absolute URL of > * a resource on the server > * > * @return the ServletContext object that > * corresponds to the named URL > * > * @see RequestDispatcher > * > */ > public ServletContext getContext(String uripath); > > > Is this test correct? > Is this the correct forum to ask this question? > > Thanks for the test suite, it is making life much easier. > > regards > > > > -- > Greg Wilkins GB Phone: +44-(0)171-4394045 > Mort Bay Consulting Australia and UK. Mbl Phone: +44-(0)7775534369 > http://www.mortbay.com AU Phone: +61-(0)299772395