Re: Importing existing JSPs etc. into new project

Jon,

if the structure is currently flat, then it should be straightforward.

The following information is from the tomcat 4.1 application developers guide 
documentation at

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/deployment.html

  To facilitate creation of a Web Application Archive file in the required 
format, it is convenient to arrange the "executable" files 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:

    a.. *.html, *.jsp, etc. - The HTML and JSP pages, along with other files 
that must be visible to the client browser (such as JavaScript, stylesheet 
files, and images) 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. 


    b.. /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. 


    c.. /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. 


    d.. /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/2.3-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 made visible to other 
classes within 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 (or installation of global library files in your server) will 
be necessary.

  Much of this information was extracted from Chapter 9 of the Servlet API 
Specification, version 2.3, which you should consult for more details.

cheers

Colin.W


----- Original Message ----- 
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, December 18, 2003 5:29 PM
Subject: RE: [WDSCI-L] Importing existing JSPs etc. into new project


> >> Are the jsps etc in the standard directory structure for a j2EE web
> project at the moment?
> 
> No - everything is in a single directory.
> 
>  >> Is JSPs, html in the public folders, java classes and libs inside
> WEB-INF?
> 
> Nope - as I say everything is flat.  I would move them to the web-inf etc.
> but there are subfolders in there so I haven't a clue which to use.  Foolish
> me though that the wizards would be smart enough to do that for me!
> 
> Jon Paris
> Partner400
> www.Partner400.com
> 
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>