Hi Doug,
Thank for the information. Did you use Tomcat 4.1.27 version? I did not use the
manager to restart the web component. What I did is following:
1) stop tomcat, remove the myApp.war, and the myApp directory.
2) copy the new myApp.war into the webapps directory.
3) start tomcat.
When I
Kam,
It is 4.1.29
This is the server.xml section for my app.
Context className=org.apache.catalina.core.StandardContext
cachingAllowed=true
charsetMapperClass=org.apache.catalina.util.CharsetMapper cookies=true
crossContext=true debug=0 displayName=golf
Hi
Have you add allowLinking=true in your Context path ?
Philippe
-Message d'origine-
De : Kam Lung Leung [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 8 avril 2004 23:54
À : [EMAIL PROTECTED]
Objet : Can someone help me
Thank Subir,
The link does help me to fix the problem. After creating a context for my web
component DistributedInputOutput in the server.xml file. Tomcat is no longer
unpack my web componemt DistributeInputOutput.war at startup. Tomcat complains
the directory is not accessible. In fact Tomcat
Kam,
Your war file should still get unpacked. Having a context defined will
not affect that. You probably have a misconfiguration in your
server.xml. If you post your server.xml here then someone may spot the
problem.
Subir
-Original Message-
From: Kam Lung Leung [mailto:[EMAIL
Kam,
The existence of a context in the server.xml will not prevent Tomcat from
unpacking a war. I have a development box that has the context defined and
the manager can undeploy and deploy the war just fine. Also restart is not
required.
What Tomcat will not do is unpack any war for which a
http://marc.theaimsgroup.com/?l=tomcat-userm=105159411609623w=2
-Original Message-
From: Kam Lung Leung [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 2:54 PM
To: [EMAIL PROTECTED]
Subject: Can someone help me to fix the soft link problem in Tomcat
4.1.27
Hi,
I installed
