In Tomcat documentation you can find the following and everything else
you might need:
There3.2 Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required
format, it is convenient to arrange the "executable" version of your web
application (that is, the files that Tomcat actually uses when executing
your app) in the same organization as required by the WAR format itself.
To do this, you will end up with the following contents in your
application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other
files that must be visible to the client browser (such as JavaScript and
stylesheet files) for your application. In larger applications you may
choose to divide these files into a subdirectory hierarchy, but for
smaller apps, it is generally much simpler to maintain only a single
directory for these files.
* WEB-INF/web.xml - The Web Application Deployment Descriptor for
your application. This is an XML file describing the servlets and other
components that make up your application, along with any initialization
parameters and container-managed security constraints that you want the
server to enforce for you. This file is discussed in more detail in the
following subsection.
* WEB-INF/classes/ - This directory contains any Java class files
(and associated resources) required for your application, including both
servlet and non-servlet classes, that are not combined into JAR files.
If your classes are organized into Java packages, you must reflect this
in the directory hierarchy under WEB-INF/classes/. For example, a Java
class named com.mycompany.mypackage.MyServlet would need to be stored in
a file named WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* WEB-INF/lib/ - This directory contains JAR files that contain
Java class files (and associated resources) required for your
application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2-compatible
server), the classes in the WEB-INF/classes/ directory, as well as all
classes in JAR files found in the WEB-INF/lib/ directory, are added to
the class path for your particular web application. Thus, if you include
all of the required library classes in one of these places (be sure to
check licenses for redistribution rights for any third party libraries
you utilize), you will simplify the installation of your web application
-- no adjustment to the system class path will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API
Specification, version 2.2, which you should consult for more details.
Armin
> -----Original Message-----
> From: Jason Hicks [SMTP:[EMAIL PROTECTED]]
> Sent: 10, sijeèanj 2001 22:18
> To: [EMAIL PROTECTED]
> Subject: Tomcat, IIS, and Adding Classes for Tomcat to use
>
> I've recently installed and configured Tomcat to work with IIS and can
> get
> the example pages working fine. I want IIS to serve my static pages,
> and
> send my JSP requests to tomcat
>
> I've got some applications in the webroot of IIS that I want to add
> some
> JSP pages to, but I can't seem to configure Tomcat correctly. I have
> some
> Java classes that I want the pages to utilize, but it appears Tomcat
> can't
> find my classes.
>
> Where do I put them? Any other configuration that needs to be done?
>
> Thanks for the help,
>
> Jason
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
