My working assumption (and web.xml seems to be happy with it) is that 
the canonical name of a servlet and it's class are the same thing. 
Thus, for servlet-name think class name.  For servlet-class, you want 
the full class path.  And so, if your servlet-name is 'nData', your 
servlet-class should be 'se.tj.activity.servlets.NServlet.nData'.

The distinction in the terminology of web.xml is sometimes a little 
confusing, but think in terms of a program on your system.  The program 
name is foo, but the full pathname is /usr/local/bin/foo, or whatever. 
And that's pretty much what you need to do in web.xml.

-- Rob

--On Monday, March 05, 2001 04:28:01 PM +0100 
[EMAIL PROTECTED] wrote:

> Hi,
> Can someone please tell me whats wrong with this web.xml file?
>
>
> <servlet>
>
>
> <servlet-name>nData</servlet-name>
>
>
> <servlet-class>se.tj.activity.servlets.NServlet</servlet-class>
>
>
> </servlet>
>
>
> <servlet-mapping>
>
>
> <servlet-name>nData</servlet-name>
>
>
> <url-pattern>/se/tj/activity/servlets/nData</url-pattern>
>
>
> </servlet-mapping>
>
>
> The servlet is in the
> \webapps\Activety\WEB-INF\classes\se\tj\activity\servlets directory
> and the servlet class is in a package called se.tj.activity.servlets.
>
>
> Thanks!
>
>
> /Lisa
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>




       _ _ _ _           _    _ _ _ _ _
      /\_\_\_\_\        /\_\ /\_\_\_\_\_\
     /\/_/_/_/_/       /\/_/ \/_/_/_/_/_/  QUIDQUID LATINE DICTUM SIT,
    /\/_/__\/_/ __    /\/_/    /\/_/          PROFUNDUM VIDITUR
   /\/_/_/_/_/ /\_\  /\/_/    /\/_/
  /\/_/ \/_/  /\/_/_/\/_/    /\/_/         (Whatever is said in Latin
  \/_/  \/_/  \/_/_/_/_/     \/_/              appears profound)

  Rob Tanner
  McMinnville, Oregon
  [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to