Re: problem on deployment

more information. Post it and they will come. rls Billy Ng [EMAIL PROTECTED] 10/21/2002 11:04 PM Please respond to Tomcat Users List To: [EMAIL PROTECTED] cc: Subject:problem on deployment I newly installed the tomcat 4.1.12. I have a war file

Re: problem on deployment

: problem on deployment If you view it with the manager app does it show it as running? I assume that you are trying to access it via http stand-alone at port 8080. What does your directory structure for your webapp look like? Do you have a WEB-INF directory with a web.xml file, etc, etc

Re: problem on deployment

PROTECTED] 10/22/2002 09:31 AM Please respond to Tomcat Users List To: Tomcat Users List [EMAIL PROTECTED] cc: Subject:Re: problem on deployment It has everything it need to run becuase the war file was ruuning fine in 4.0.3. How can I check it in manager app

Re: problem on deployment

If you copied the war file to the TOMCAT_HOME/webapps directory, TC should recognize it and expand it for you. Is it expanded? Look in the webapps directory, do you see a new directory there with the same name as your war file?. If you still have the Tomcat http connector running then go to

Re: problem on deployment

In ${CATALINA_HOME}/conf/tomcat-user.xml, add a user and a role like this user name=XXX password=XXX roles=manager / Then restart Tomcat. -- Jeanfrancois Billy Ng wrote: If you copied the war file to the TOMCAT_HOME/webapps directory, TC should recognize it and expand it for you. Is it

problem on deployment

I newly installed the tomcat 4.1.12. I have a war file that works okay with tomcat 4.0.3. After I deployed this war file to the tomcat 4.1.12 webapps directory, I got the 404 page, why? Do I need to something different on deployment with 4.1.12? Thanks! Billy Ng

Re: Problem writing deployment Servlet

] cc: Subject:Problem writing deployment Servlet I didn't get any replies on this question, so I thought I would try again. I recently tried building a deployment tool by implementing the ContainerServlet and had some problems. When I first tried to access the Servlet, I got

RE: Problem writing deployment Servlet

: Problem writing deployment Servlet This is a possibility. But, the problem with this solution, is that it assumes certain file system priveledges. Also, I think calling a Java API from a web application would be much cleaner. Thanks for the suggestion, though. Scott = Original Message From

Problem writing deployment Servlet

I didn't get any replies on this question, so I thought I would try again. I recently tried building a deployment tool by implementing the ContainerServlet and had some problems. When I first tried to access the Servlet, I got the following exception: java.lang.NoClassDefFoundError:

Problem writing deployment Servlet (was Re: Deploying Web Application Programmatically)

Thank you for your suggestions. A URL connection to the manager application is an option, but I think the Servlet option better fulfils my requirements. I recently tried building the tool using an implementation of the ContainerServlet and had some problems. When I first tried to access the

Problem With Deployment of Web Application in Tomcat

Hi Everyone, When i Tried to deploy a web application that uses xml.jar, tomcat overrides my xml.jar withits own parser.jar from its library. Is there a way i can override this behaviour. Thanks Vijay

Re: Problem With Deployment of Web Application in Tomcat

The only way I know of to handle this is what the Cocoon install documentation suggests -- renamed parser.jar to z_parser.jar so that it comes *after* xml.jar in the automatically-generated classpath. I am not sure if this introduces any possible errors, however... I also haven't thought about

RE: Problem With Deployment of Web Application in Tomcat

., San Jose, CA 95131 Tel: 408-944-1500 ext. 651 Fax: 408-944-1599 [EMAIL PROTECTED] -Original Message- From: Michael J. Suzio [mailto:[EMAIL PROTECTED]] Sent: Monday, November 27, 2000 12:58 PM To: [EMAIL PROTECTED] Subject: Re: Problem With Deployment of Web Application in Tomcat The only