Defining a webapp in Tomcat 4.0

Hello there:
can anyone give me a good tight example or lesson on defining and deploying a webapp on the Tomcat server in a standalone situation? Currently I can view and use
my JSP apps on Tomcat by creating a directory and placing the files within it. However the servlets that my pages use are not visible to the server. I'm sure this has to do with the server.xml and web.xml config files but I've been up for too many days and I'm just looking for the answer.... :)
Thanks in advance
Justin

Hi
Suppose you have directory mydir in D:\ , then you can add following line in server.xml file of conf folder of tomcat.
<Context path="/mycontext"
docBase="D:\mydir"
crossContext="false"
debug="0"
reloadable="true" >
</Context>
Now suppose u have test.jsp in mydir folder, the u can invoke this jsp in browser as follow
http://localhost:8080/mycontext/test.jsp
Try it !
Kind Regards
Chetan Chandarana

Similar Messages

Deploy problem of JSF WebApp on Tomcat 5.5.17 SEVERE: Error listenerStart

Hi there,
My installation configuration is as followed:
Tomcat5.5.17 using the following connector:
    <Connector
      port="8083"
      maxHttpHeaderSize="8192"
      maxThreads="150"
      minSpareThreads="25"
      maxSpareThreads="75"
      enableLookups="true"
      redirectPort="8080"
      acceptCount="100"
      debug="1"
      connectionTimeout="20000"
      disableUploadTimeout="true" />tomcat-user.xml defines:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="admin"/>
<user username="tomcat" password="tomcat" roles="manager,admin"/>
</tomcat-users>Tomcat starts up correctly with the following url and is runs while deploying:
http://localhost:8083/manager/html
My WebApp is a simple Test App and is the following:
index.html:
<html>
   <head>
      <meta http-equiv="Refresh" content= "0; URL=index.faces"/>
      <title>Start Web Application</title>
   </head>
   <body>
      <p>Please wait for the web application to start.</p>
   </body>
</html>
index.jsp:
<html>
   <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
   <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
   <f:view>
      <head>
         <title>A Simple JavaServer Faces Application</title>
      </head>
      <body>
         <h:form>
            <h3>Please enter your name and password.</h3>
            <table>
               <tr>
                  <td>Name:</td>
                  <td>
                     <h:inputText value="#{user.name}"/>
                  </td>
               </tr>
               <tr>
                  <td>Password:</td>
                  <td>
                     <h:inputSecret value="#{user.password}"/>
                  </td>
               </tr>
            </table>
            <p>
               <h:commandButton value="Login" action="login"/>
            </p>
         </h:form>
      </body>
   </f:view>
</html>welcome.jsp:
<html>
   <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
   <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
   <f:view>
      <head>
         <title>A Simple JavaServer Faces Application</title>
      </head>
      <body>
         <h:form>
            <h3>
               Welcome to JavaServer Faces,
               <h:outputText value="#{user.name}"/>!
            </h3>
         </h:form>
      </body>
   </f:view>
</html>
UserBean.java:
package com.jsfcore;
public class UserBean {
     private String name;
     private String password;
     public UserBean() {
          super();
     private String getName() {
          return this.name;
     private void setName(String name) {
          this.name = name;
     private String getPassword() {
          return this.password;
     private void setPassword(String password) {
          this.password = password;
web.xml:
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC
   "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
   "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
   <display-name>Simple Login Applications</display-name>
   <servlet>
      <servlet-name>Faces Servlet</servlet-name>
      <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
   </servlet>
   <servlet-mapping>
      <servlet-name>Faces Servlet</servlet-name>
      <url-pattern>/faces/*</url-pattern>
   </servlet-mapping>
   <welcome-file-list>
      <welcome-file>index.html</welcome-file>
   </welcome-file-list>
</web-app>
faces-config.xml:
<?xml version="1.0"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
"http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
<faces-config>
   <navigation-rule>
      <from-view-id>/index.jsp</from-view-id>
      <navigation-case>
         <from-outcome>login</from-outcome>
         <to-view-id>/welcome.jsp</to-view-id>
      </navigation-case>
   </navigation-rule>
   <managed-bean>
      <managed-bean-name>user</managed-bean-name>
      <managed-bean-class>com.corejsf.UserBean</managed-bean-class>
      <managed-bean-scope>session</managed-bean-scope>
   </managed-bean>
</faces-config>I have downloaded jsf-1_1_01.zip and installed it.
I have downloaded java_ee_sdk-5-windows.exe and installed it too.
Path login/WEB-INF/lib contains the following jars:
jsf/lib/jsf-api.jar
jsf/lib/jsf-impl.jar
tomcat/servler/lib/commons-digester.jar (fr. tomcat 4.1.3)
tomcat/server/lib/commons-beanutils.jar (fr. tomcat 4.1.3)
tomcat/webapps/jsp-examples/lib/jstl.jar (fr. tomcat 5.5.17)
tomcat/webapps/jsp-examples/lib/standard.jar (fr. tomcat 5.5.17)
The compilation and deployment was successful.
With my build.xml, I have deployed the login.war file into path
tomcat/webapps
The login.war file was unpacked into the normal web application directory structure.
That is where the problem appeared with the output display on the consol:
Jul 27, 2006 11:10:39 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8083
Jul 27, 2006 11:10:39 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8082
Jul 27, 2006 11:10:39 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 750 ms
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jul 27, 2006 11:10:41 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive login.war
Jul 27, 2006 11:10:41 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jul 27, 2006 11:10:41 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [login] startup failed due to previous errors
Jul 27, 2006 11:10:42 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8083
Jul 27, 2006 11:10:42 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8082
Jul 27, 2006 11:10:42 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Jul 27, 2006 11:10:43 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3047 ms
I am unable to start the login application on the Tomcat Web Application Manager.
The following Message appears on top:
FAIL - Application at context path /login could not be started
Let me say, that I have already continued developing more code for this application up to this point and wanted to test in the meantime. Since I had this failure I mentioned above, I have stripped down the application to the code above and I still have no success. I cannot go further until I am getting this very small application up and running on the server.
Is anybody out there who could give me a hint to solve this problem?
I really appreciate any hints, since I am circeling around the problem for guit a while.
Thanks very much
Markus

Hi there,
My installation configuration is as followed:
Tomcat5.5.17 using the following connector:
    <Connector
      port="8083"
      maxHttpHeaderSize="8192"
      maxThreads="150"
      minSpareThreads="25"
      maxSpareThreads="75"
      enableLookups="true"
      redirectPort="8080"
      acceptCount="100"
      debug="1"
      connectionTimeout="20000"
      disableUploadTimeout="true" />tomcat-user.xml defines:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="admin"/>
<user username="tomcat" password="tomcat" roles="manager,admin"/>
</tomcat-users>Tomcat starts up correctly with the following url and is runs while deploying:
http://localhost:8083/manager/html
My WebApp is a simple Test App and is the following:
index.html:
<html>
   <head>
      <meta http-equiv="Refresh" content= "0; URL=index.faces"/>
      <title>Start Web Application</title>
   </head>
   <body>
      <p>Please wait for the web application to start.</p>
   </body>
</html>
index.jsp:
<html>
   <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
   <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
   <f:view>
      <head>
         <title>A Simple JavaServer Faces Application</title>
      </head>
      <body>
         <h:form>
            <h3>Please enter your name and password.</h3>
            <table>
               <tr>
                  <td>Name:</td>
                  <td>
                     <h:inputText value="#{user.name}"/>
                  </td>
               </tr>
               <tr>
                  <td>Password:</td>
                  <td>
                     <h:inputSecret value="#{user.password}"/>
                  </td>
               </tr>
            </table>
            <p>
               <h:commandButton value="Login" action="login"/>
            </p>
         </h:form>
      </body>
   </f:view>
</html>welcome.jsp:
<html>
   <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
   <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
   <f:view>
      <head>
         <title>A Simple JavaServer Faces Application</title>
      </head>
      <body>
         <h:form>
            <h3>
               Welcome to JavaServer Faces,
               <h:outputText value="#{user.name}"/>!
            </h3>
         </h:form>
      </body>
   </f:view>
</html>
UserBean.java:
package com.jsfcore;
public class UserBean {
     private String name;
     private String password;
     public UserBean() {
          super();
     private String getName() {
          return this.name;
     private void setName(String name) {
          this.name = name;
     private String getPassword() {
          return this.password;
     private void setPassword(String password) {
          this.password = password;
web.xml:
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC
   "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
   "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
   <display-name>Simple Login Applications</display-name>
   <servlet>
      <servlet-name>Faces Servlet</servlet-name>
      <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
   </servlet>
   <servlet-mapping>
      <servlet-name>Faces Servlet</servlet-name>
      <url-pattern>/faces/*</url-pattern>
   </servlet-mapping>
   <welcome-file-list>
      <welcome-file>index.html</welcome-file>
   </welcome-file-list>
</web-app>
faces-config.xml:
<?xml version="1.0"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
"http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
<faces-config>
   <navigation-rule>
      <from-view-id>/index.jsp</from-view-id>
      <navigation-case>
         <from-outcome>login</from-outcome>
         <to-view-id>/welcome.jsp</to-view-id>
      </navigation-case>
   </navigation-rule>
   <managed-bean>
      <managed-bean-name>user</managed-bean-name>
      <managed-bean-class>com.corejsf.UserBean</managed-bean-class>
      <managed-bean-scope>session</managed-bean-scope>
   </managed-bean>
</faces-config>I have downloaded jsf-1_1_01.zip and installed it.
I have downloaded java_ee_sdk-5-windows.exe and installed it too.
Path login/WEB-INF/lib contains the following jars:
jsf/lib/jsf-api.jar
jsf/lib/jsf-impl.jar
tomcat/servler/lib/commons-digester.jar (fr. tomcat 4.1.3)
tomcat/server/lib/commons-beanutils.jar (fr. tomcat 4.1.3)
tomcat/webapps/jsp-examples/lib/jstl.jar (fr. tomcat 5.5.17)
tomcat/webapps/jsp-examples/lib/standard.jar (fr. tomcat 5.5.17)
The compilation and deployment was successful.
With my build.xml, I have deployed the login.war file into path
tomcat/webapps
The login.war file was unpacked into the normal web application directory structure.
That is where the problem appeared with the output display on the consol:
Jul 27, 2006 11:10:39 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8083
Jul 27, 2006 11:10:39 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8082
Jul 27, 2006 11:10:39 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 750 ms
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.17
Jul 27, 2006 11:10:40 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jul 27, 2006 11:10:41 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive login.war
Jul 27, 2006 11:10:41 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jul 27, 2006 11:10:41 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [login] startup failed due to previous errors
Jul 27, 2006 11:10:42 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8083
Jul 27, 2006 11:10:42 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8082
Jul 27, 2006 11:10:42 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Jul 27, 2006 11:10:43 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3047 ms
I am unable to start the login application on the Tomcat Web Application Manager.
The following Message appears on top:
FAIL - Application at context path /login could not be started
Let me say, that I have already continued developing more code for this application up to this point and wanted to test in the meantime. Since I had this failure I mentioned above, I have stripped down the application to the code above and I still have no success. I cannot go further until I am getting this very small application up and running on the server.
Is anybody out there who could give me a hint to solve this problem?
I really appreciate any hints, since I am circeling around the problem for guit a while.
Thanks very much
Markus

Setting different JDK versions for Different webapp in Tomcat

Hi All,
I have 2 web-applications in Tomcat 5. Now for Java I have j2sdk1.4.2 & j2sdk1.3..
Now One of my application needs j2sdk1.4.2 while other can run only with
j2sdk1.3.. (This is an old project & there are java class package norms - like every class should be in a package to import it now. But earlier it was not strict).
Means this is absoulte for me to run one application with version 1.3 while other with 1.4.
But I can set Java_Home env. varibale only once. How can I tell my each web-application to take thier own jdk version in compiling & running.
Is this allowed in J2EE/Web-Containers.
Please suggest if there is any such setting which makes it possible.
THanks you all in advance...
Manoj :confused:

wouldn't matter if you could.
The package enforcement is NOT something from J2SDK 1.4 but from the version of Tomcat used.
Each Tomcat instance will use the same JVM for all webapps running inside it. You'll need a separate Tomcat instance of an older version for the older webapp (or better yet change it around to the new rules).

Not able to export file as .war to webapps in tomcat home

Below is my first servlet program:
FirstServlet.java:
package edu.aspire;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.Servlet;
import javax.servlet.ServletConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
public class FirstServlet implements Servlet {
static {
System.out.println("Loading Servlet");
public FirstServlet() {
System.out.println("Instantiating Servlet");
public void init(ServletConfig config) throws ServletException {
System.out.println("Initializing Servlet");
public void destroy() {
System.out.println("Removing Servlet from the Servlet container");
public ServletConfig getServletConfig() {
return null;
public String getServletInfo() {
return null;
public void service(ServletRequest request, ServletResponse response)
throws ServletException, IOException {
System.out.println("service() method");
PrintWriter out = response.getWriter();
out.println("Hello World!");
web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
<servlet>
    <servlet-name>aspire</servlet-name>
    <servlet-class>edu.aspire.FirstServlet</servlet-class>
</servlet>
<servlet-mapping>
    <servlet-name>aspire</servlet-name>
    <url-pattern>/first</url-pattern>
</servlet-mapping>
</web-app>
Deployement:
To deploy my project into %TOMCAT_HOME%\webapps folder.
Right click on Project ->Export-> War File
Project Name: Hello
Destination: D:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\Hello.war
Result found in web browser:
HTTP Status 404 - /Hello/first
And Hello.war file is not found in webapps folder too after exporting as .war.
I am using Apache tomcat 6.0.37, eclipse 3.7.2 release, tomcat plugin :com.sysdeo.eclipse.tomcat_3.3.0
Please let me know where i am going wrong.

I have done all those settings but still read the 'Eclipse tomcat run time' and repeated the settings accordingly. Still not not getting output.
-I exported the file to destination webapps folder and clicked 'finish'
-when i select 'run on server'
-the tomcat gets started and 'http status 404' page is displayed in browser
I even tried this
- manaully started server
-exported as .war file to webapps but does not get exported, doesnt get deployed and nothing gets displayed in the console
-when provide the link the same page is displayed
One alert message is displayed in the markers 'Classpath entry C:/Program Files/Apache Software Foundation/Tomcat 6.0/lib/servlet-api.jar will not be exported or published. Runtime ClassNotFoundExceptions may result.'
I have added servlet-api.jar to the library but still getting this message so tried to adding in classpath (as provided in websites) that also didnt work.
Next what to do i dont understand.

Defining a context in Tomcat 5.5.4

I've just setup tomcat 5.5.4 with a plan to migrate my webapps to it from tomcat 5.0.16.
However, under tomcat 5.0.16, you could specifiy a separate xml file in the catalina/localhost folder which held your webapps context info.
Doing this under tomcat 5.5.4 just doesn't seem to work, and I've had to go back to the 'old' tomcat 4 way of adding the <context> directly into the server.xml file, which when cut and paste, works perfectly.
So am I missing something, or did they decide to revert to that mechanism ?

Ok, I thought that link looked familiar, but it still doesn't help..
Here is my <context>.. this works perfectly under 5.0 as a separate xml file in the catalina/localhost folder, but under 5.5, I can only get this context to load by adding it directly to the server.xml...
     <Context path="" docBase="D:\dev\Projects\newk00l\website\games\" reloadable="true" crossContext="false">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_k00l_log." suffix=".txt"
     timestamp="true"/>
<Resource name="jdbc/netk00lextreme" auth="Container"
type="javax.sql.DataSource" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost/k00l_extreme?autoReconnect=true"
username="myusername" password="mypassword" maxActive="20" maxIdle="10" maxWait="-1"/>
     </Context>

How to enable https for a single webapp in tomcat 5.5 ?

Hi ,
I want to enable https for my web app in Tomcat 5.5(with JDK 1.5, in WinXP) without affecting other webapps running in the same server . Any idea how to do it ? Pl. note , I dont want to make the entire tomcat as SSL enabled.
Regards
Diana

You specify SSL in web.xml of your application. So, in that case other web applications in same server would not be affected.
<security-constraint>
<web-resource-collection>
<web-resource-name>myresources</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>Following link will help you to setup SSL in tomcat:
[http://techtracer.com/2007/09/12/setting-up-ssl-on-tomcat-in-3-easy-steps/|http://techtracer.com/2007/09/12/setting-up-ssl-on-tomcat-in-3-easy-steps/]
Thanks,
Mrityunjoy

Securing a different webapps in Tomcat

Dear all:
Hi I'm defining security constraints for all webapps in my ROOT web.xml deployment descriptor,
I am using several url-patterns which involve different webapps(contexts)
so I can protect all.
I added:
<url-pattern>/*</url-pattern> which defines protection for current weabapp(ROOT)
<url-pattern>/webappdir/*<url-pattern>which defines protection for any other webapp
I tried this and only ROOT context is protected(whose deployment descriptor has this definition)
is it possible to protect any other context from ROOT if so how?

Nevermind
I already solved it
thanks anyway

Request.getParameter returns null - Converting webapp from Tomcat to oc4j

I support a simple web app that passes arguments via url context variables. For some reason it does not work in OC4J. When I use request.getContextPath() I see that the URL string only contains the webapps name, not the whole URL with parameters set.
BTW it is an OC4J cluster

*Name:             index.jsp
*Function:         This page is 1st url for WebApp
*Information:      This page is used as the home page for this application.
*Version:          1.0 (created on 2005-06-06)
* 2.0 052406 pge
%>
<%@ page pageEncoding="UTF-8"%>
<%@ page import="com.hp.itsm.api.*" %>
<%@ page import="com.hp.itsm.api.interfaces.*" %>
<%@ page import="java.text.Collator" %>
<%@ page import="java.util.*"%>
<%@ page contentType="text/html; charset=utf-8" %>
<%@ include file="include/variables_initialize.jsp" %>
<%@ include file="include/methods_global.jsp" %>
<%@ include file="include/methods_servicedesk.jsp" %>
<%
String login = request.getParameter("u");
String xxx = request.getContextPath();
//Service Call objects
ApiSDSession SDsession = null;
IPerson[] personList = null;
IAccount accountRequester = null;
Boolean bError = Boolean.FALSE; //Default to no errors found
List errMsgList = new ArrayList(); //Array of error messages
//Get account information
accountRequester = getAccount(SDsession, login);
if (accountRequester == null) {
bError = Boolean.TRUE;
errMsgList.add("Could not retrieve the accountRequester.");
}

Send JMS message from a webapp in Tomcat to JMS queue in SJSAS

Hi, everybody
I have a web application. Is is a simple JMS message sender: 2 jsp files(User Interface) and a java helper class which in charge of the sending of jms messages) . It runs well on SJSAS 9 web container.
After I have moved it to Tomcat5.5.17(bundled with Netbeans5.5.1), I have the following exception when I visit the jsp page:
type : Exception report
message :
description : The server encountered an internal error () that prevented it from fulfilling this request.
exception:
javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     java.lang.Thread.run(Thread.java:595)
root cause :
java.lang.NoClassDefFoundError
     org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     java.lang.Thread.run(Thread.java:595)I have imported appserv-rt.jar / appserv-ext.jar / appserv-deployment-jar / appserv-ws.jar / imqjmsra.jar / javaee.jar to my web application's library.
And i have used the argu-ed Context to do JNDI job to find the JMS resources in SJSAS.
I need your advices, thank you.

The following is the detailed info contains in Tomcat's logs file
SEVERE: StandardWrapper.Throwable
java.lang.NoClassDefFoundError: javax/servlet/jsp/JspApplicationContext
     at org.apache.jasper.compiler.JspRuntimeContext.<clinit>(JspRuntimeContext.java:84)
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:608)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493)
     at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1204)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1377)
     at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:814)
     at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:343)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 7, 2007 1:56:10 PM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet /zzTomcat threw load() exception
java.lang.NoClassDefFoundError: javax/servlet/jsp/JspApplicationContext
     at org.apache.jasper.compiler.JspRuntimeContext.<clinit>(JspRuntimeContext.java:84)
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:608)
     at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493)
     at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1204)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1377)
     at org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:814)
     at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:343)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 7, 2007 1:57:14 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
java.lang.NoClassDefFoundError
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 7, 2007 1:57:14 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet jsp
java.lang.NoClassDefFoundError
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 7, 2007 2:07:05 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
java.lang.NoClassDefFoundError
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 7, 2007 2:07:05 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet jsp
java.lang.NoClassDefFoundError
     at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)

Webapp deployment in Tomcat 5.0

Hello. I'm having trouble deploying my simple webapp in Tomcat 5.0. Specifically, I can't hit my servlets. My directory structure looks like this:
Tomcat Home -> webapps -> myWebApp -> WEB-INF
Inside WEB-INF, I have web.xml file with servlet-mapping elements defining each servlet, along with the "classes" dir that contains my servlets.
I can run the example servlets fine by typing in: "http://localhost:8080/servlets-examples/servlet/HelloWorldExample". It's fine. However, when I try to do the same with my servlets, it can't find the mapping. I've verified that my web.xml is correct since I just copied the known good one from the examples and changed the names.
I guess my question is: Is there anything that I need to do with Tomcat's config files to tell it how to find myWebApp? All I've done is pasted the directory structure into /webapps and tried to run it. The tomcat docs didn't help me very much, unfortunately.
Any ideas?

Build a war file for your web app and put it in the webapps directory of tomcat. Then when you start the server, it would automatically explode the war into the directory structure. I know this works with Tomcat 4.0.3 . It should work with version 5 as well.
HTH

Tomcat 6 Admin Webapp Headache

Hi there,
I've just installed Tomcat 6 and am now trying to install the Admin webapp. Firstly, I couldn't find it anywhere on the tomcat website and I eventually (after loads of searching around on google) found the following:
http://www.apache.org/dist/tomcat/tomcat-5/v5.5.23/bin/apache-tomcat-5.5.23-admin.zip
Obviously this is the admin app for version 5, but I can't find anything for version 6.
I then unzipped it, and copied the webapps/admin directory to the Tomcat webapps directory. The webapp appears in the manager as started, but going to http://localhost/admin produced a blank page with the following error in the log:
WARNING: Unexpected error forwarding to login page
javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class org.apache.struts.taglib.html.HtmlTag
     at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:850)
     at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779)
     at admin.login_jsp._jspService(login_jsp.java:118)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
     at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:316)
     at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:244)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.struts.taglib.html.HtmlTag
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Unknown Source)
     at admin.login_jsp.class$(login_jsp.java:70)
     at admin.login_jsp._jspService(login_jsp.java:70)
     ... 19 moreHtmlTag definitely exists in webapps/admin/WEB-INF/lib/struts.jar
Has anyone got any idea what's going on, and/or does anyone know how to get this working?
Thanks,
Chris.

I found the following on apache's web site:
There is no admin webapp for tomcat 6 and there is no plan to implement
it. This has been answered in the archives so you could do a search for
more details on why if you need more info.
The URL to this is:
http://mail-archives.apache.org/mod_mbox/tomcat-users/200707.mbox/%[email protected]om.au%3E

Exporting a webApp installed on Tomcat

Can someone tell me how to export a webApp from tomcat so that I can use the generated war file to deploy on another AppServer.

Can someone tell me how to export a webApp from tomcat
so that I can use the generated war file to deploy on
another AppServer.You can create the war yourself using jar webapp.war webapp. Then you can copy the war file onto another server.

Problem with Configuring Tomcat for running jsp web applications..Plz HELP

I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
to connect to the database. I have placed my project folder called
tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
a collection of html pages,jsp pages and images of my project. Also I created a
WEB-INF folderand in that I have lib folder which contains catalina-root.jar
, classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
file which looks like this
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app>
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>jdbc/gdn</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
My Server.xml file in Tomcat\conf folder is as follows



<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
<Resource name="jdbc/gdn" auth="Container"
type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
url="jdbc:odbc:gdn"
username="system" password="tiger" maxActive="20" maxIdle="10"
maxWait="-1"/>
</GlobalNamingResources>


<Service name="Catalina">


<Connector
port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

     



<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />






<Engine name="Catalina" defaultHost="localhost">




<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>







<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">









<Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
</Host>
</Engine>
</Service>
</Server>
I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
in a browser. Here I accept a username and password from the user and then do the validation in
a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
accordingly. However when I enter the username and password and click Go in the homepage, nothing is
displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
IS IT POSSIBLE?WHY WILL THIS HAPPEN?
I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
Is there any other thing that I need to set in classpath? Should I have my project as a
WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
to connect to the database. I have placed my project folder called
tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
a collection of html pages,jsp pages and images of my project. Also I created a
WEB-INF folderand in that I have lib folder which contains catalina-root.jar
, classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
file which looks like this
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app>
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>jdbc/gdn</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
My Server.xml file in Tomcat\conf folder is as follows



<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
<Resource name="jdbc/gdn" auth="Container"
type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
url="jdbc:odbc:gdn"
username="system" password="tiger" maxActive="20" maxIdle="10"
maxWait="-1"/>
</GlobalNamingResources>


<Service name="Catalina">


<Connector
port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

     



<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />






<Engine name="Catalina" defaultHost="localhost">




<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>







<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">









<Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
</Host>
</Engine>
</Service>
</Server>
I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
in a browser. Here I accept a username and password from the user and then do the validation in
a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
accordingly. However when I enter the username and password and click Go in the homepage, nothing is
displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
IS IT POSSIBLE?WHY WILL THIS HAPPEN?
I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
Is there any other thing that I need to set in classpath? Should I have my project as a
WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

JSP include directive not working with Tomcat 5.0

Hi.
I'm developing a small JSF webapp under Tomcat 5.0. My idea was to use the include directive to display a navigation panel on every JSP page.
I took the code straight from the Java Web Services Tutorial; the resulting page looks like this:
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
       version="2.0">
<jsp:directive.page contentType="text/html;charset=iso-8859-1"/>
<%@ include file="/jsp/panelpage_header.inc" %>
     <h:outputText value="Welcome!"/>
<%@ include file="/jsp/panelpage_footer.inc" %>
</jsp:root>However, when I try to load the page, a compilation error occurrs:
org.apache.jasper.JasperException: /trias/welcome2.jsp(11,2) The content of elements must consist of well-formed character data or markup.
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
...I checked the path to the included files, and it seems to be okay. The files themselves contain the JSF tags for the view, html-head, html-body etc. The compiler doesn't even care if the files exist or not because it aborts immediately when it reaches the first include-statement.
Did anyone see this kind of error before?

Ok, the solution with jsp:directive.include works,
if header.inc and footer.inc themselves are well
formed too. If I understood the concept right this is
because header and footer are processed during
request time and therefore interpreted as
'standalone' pages.This isn't true. The include directive (<jsp:directive.include>) is run a Compile Time. The code is inserted directly into the surrounding JSP (unlike <jsp:include> which forwards the request at runtime). The finished JSP, after the include, is then processed and needs to be well-formed XML.
>
But: What can I do when these two files define a tag
that should enclose my current page (for example,
header opens a panelGrid-Tag, and footer closes it).
For this case I thought the use of the
@include-directive would be neccessary to combine the
three pages during compilation. By this the resulting
page would be well-formed although header and footer
are not.It should be, as long as you are using <jsp:directive.include>, and the rest of the included pages are also well formed (no <% %> tags, nothing else out of place...).
Honestly, I haven't done much work with JSP documents, so I haven't run into this problem. But I do believe everything I said is correct.
What I would do is double check the correctness of the rest of the included pages and see if your error isn't something else.

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
     Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
     Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
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:
* *.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.
* /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/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.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

Defining a webapp in Tomcat 4.0

Similar Messages

Maybe you are looking for